i am using IIS in a visual studio 2010 solution with Integrated 4.0 and 2.0 Classic web pools. when i use IE 11 over the Inet to "try" and login, the app fails.
yes i know about changing settings but this cannot happen on my web site. Any thoughts on what is happening and / or why?
i have not tried to bring up the app using IE 11, any ideas on the "surprises" i will find? thanks for any comments, they are appreciated.
I had the same issue using VS2010. I knew this problem existed with IE 10 and I somehow let the automatic updates install IE 11.
I found this fix from MS and it resolved the issue for me:
http://blogs.msdn.com/b/visualstudioalm/archive/2013/09/17/coded-ui-mtm-issues-on-internet-explorer-with-kb2870699.aspx
My apologies if this is wide of the OP's question, but I also had problems using Studio 2010 with the new IE 11 (googling those two terms led me here, and John B's post led me to answer). Specifically Studio's debugger would fail to attach to IE 11 while I was launching a Silverlight project.
John B linked to an MSDN patch. After I installed it, Studio still would fail to attach to IE11, but at least this time I got an error message: "The 32-bit version of the Visual Studio Remote Debugging Monitor (MSVSMON.EXE) cannot be used to debug 64-bit processes or 64-bit dumps. Please use the 64-bit version instead."
From that message I found out that Silverlight can only run in 32-bit mode. And both IE10 and IE11 cannot run in 32-bit mode when they place all the tabs into a single 64-bit process. However, if "Enhanced Protected Mode" is enabled (which it was for me by default, it's under Internet Options' Security tab) and you change this registry value...
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\TabProcGrowth
...to be something more than 0 (I set mine to 5, not sure it matters much as long as it's more than 0), then IE11 is able to spawn 32-bit processes and Studio is able to launch a 32-bit browser instance that it can attach the Silverlight debugger to.
A few related articles...
http://support.microsoft.com/kb/2716529
https://superuser.com/questions/561036/unable-to-open-ie-10-in-32-bit-mode
http://connect.microsoft.com/VisualStudio/feedback/details/774460/cannot-debug-silverlight-win7-x64-ie10
Hope this helps someone.
Related
I am using crystal report v10.5 with visual studio 2008 to develop crystal reports.The problem I am facing is with the toolbar which is not visible on Firefox but it is visible on IE and Chrome.
I have installed same version on both development machine and on production server which is Crystal report v10.5. My development machine is Windows 7 32bit and production is Windows 2008 64bit.
I have tried solutions mentioned on numerous forums such as
Copy the 'aspnet_client' folder from 'C:\Inetpub\wwwroot' to 'C:\Inetpub\wwwroot\your-website-name'.
create a new virtual directory in your web site and point it to "C:/Inetpub/wwwroot/aspnet_client".
Application pool is to be changed to "Classic" instead of "Integrated".
Set the application pool of your application to operate under LOCAL SERVICE permission.
But still I am not able to show toolbar on Firefox.
Configurations:
Visual Studio 2008
.Net Framework 3.5
Crystal Report for runtime 10.5
Windows Server 2008 64bit
Can anyone point me to the right direction?
Edit- I recently upgraded from Windows 2003 to Windows 2008 and the same version for CR 10.5 was working as expected without any mentioned solutions above.
Thank you
You need to add ClientTarget="uplevel" to the page directive of the aspx file.
<%# Page ClientTarget="uplevel" ... %>
It seems that there are compatibility issues between CR and certain browsers depending on the version of CR. There is a very helpful post here that has links to a compatibility table. I suggest to check that out and then see if you can maybe upgrade to a different version of CR.
Hope that helps.
My application use last Crystal Runtime on x64 server and work on firefox too.
1) If the toolbar is not visible there should be a reason (press F12 in firefox.. what do you see? 404 error? 500 error? Please post it!)
2) Crystal Reports Runtime 13.x IS available for X64 servers too.. There is no reason to use an old runtime containing many bugs resolved in other releases.
You can get it here (get MSI 64 bit - Support Pack 8)
After updating runtime you have to copy the 'aspnet_client' folder again fi you did (new virtual directory in your web site is a better approach)
After updating runtime you could need a little hack to let an application developed with older dll work with new dll. There are few rows you have to put into web.config described here.
My task is simple: I need to test my ASP.NET web application in a 64-bit environment on my development machine. (At this point I don't even ask about running it through a debugger. All I need is to run it in a 64-bit process.)
So I created a stock C# Web Application in Visual Studio 2010 and adjusted its properties as such:
I then did Ctrl+F5 (or run without debugging) and IE loaded up and hangs up like so:
What am I doing wrong here?
PS. Running it on Windows 7 Ultimate (64-bit).
We had the same problem and when the team jumped to Visual Studio 2012, this registry key was really useful to us :
you can add a registry key to force visual studio to use the 64 bits version of iisexpress.exe ; unfortunately for you, it is a VS2012-only solution.
reg add HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\WebProjects
/v Use64BitIISExpress /t REG_DWORD /d 1
Then restart Visual Studio and tick [X] Use IIS Express in your settings.
(see also the source).
UPDATE: For reference, in Visual 2013, this option can be found in the interface : Options/Projects and Solutions/Web Projects/Use the 64 bit version of IIS Express for web sites and projects
In IIS make sure the Application Pool, Advance Settings, Enable 32-Bit Applications = false
If this setting is true then the worker process will run as 32bit WOW64 process.
Chris
No settings required in project or solution level. I am developing WebApp on VS2010 on 32 bit and 64-bit machines simultaneously. Actually We are working on SVN and our few machines have Win7 32-bit and my few mates have Win7-64bit laptops. But there we haven't faced any such issue while compiling the app on two different machines and Even on the live server, it runs butter smooth. Hardly care about the bit and bytes.
To verify a test run. Publish your code and host in your local IIS or Cassini Webserver and access it over LAN.
Also if possible revert back solution and project settings to its original configuration settings. Generally, We do not need to change target until and unless it is strictly required. As, AFAIK, It compiles the assembly under "Any CPU" as target, which is eligible for all i.e. IA, X64 and X86..
Finally, if you are coming across any error, please do post it here. It will help you and us as well.
First of all how to do you know if your IIS process is running your website as 32-bit or 64-bit as of now?
Open Task manager to check the bitness of w3wp.exe. If your machine is 64-bit then IIS will run 64-bit by default. Your problem seems to be something else. If bitness is the issue then you won't even come this far. Check IIS logs (c:\inetpub\logs{website-ID}{date})... that might give you some pointers. If there is nothing in there, check event viewer. If nothing then check if the virtual directory is actually created in IIS Manager under Default Web Site.
Have you actually tested if IIS (sans ASPX) is functional? http:// localhost ? does that work? if that is working then I would recommend checking if your ASP.NET modules are properly installed within IIS.
Hope this Helps.
I'm developing an ASP.NET MVC 4 site using Visual Studio 2012 Premium on Windows 8 RTM x64. When I right click on the web application and choose Publish, Visual Studio 2012 returns the message:
"fail to open url of 'http://.../'.
Exception:Class not registered"
The publish process seems to work correctly but it fails to launch the browser. This happens every time I try to Publish the site and it happens with Chrome (21.0.1180.79 m) or Firefox (14.0.1).
Furthermore, since the site isn't launching post Publish, I do it manually using Ctrl-F5. I'm able to navigate around the site normally, but if I right click on the browser's icon on the task bar to launch another browser instance, nothing happens. Once I close all browser instances, the browser task bar icon reverts to its normal behavior.
I'm not sure if these two issues are related, but the common theme here is launching a browser from Visual Studio 2012 causes unexpected side effects. The browser either fails to launch on Publish or launches with Ctrl-F5 but renders launching another instance useless using the task bar icon.
Any help is appreciated.
EDIT: I've re-installed the entire software stack (Windows 8, Office 2010, Visual Studio 2012, Windows Update, Chrome, Firefox). The above issues continue, unless I make Internet Explorer the default browser.
Thanks.
I filed a Chrome bug, it was a browser registration thing. If you uninstall and reinstall from a Download and be SURE to say Yes to the UAC prompt, Chrome will register Machine Wide, rather than User. That is required to launch as Admin. (HKLM vs. HKCU)
It appears this problem is much more widespread than the Web Publish operation. Anytime you use the ShellExecute() API (or Process.Start) to access a URL it fails when running under elevated rights (ie. Run As Administrator).
I see this in any application that uses Process.Start() or ShellExecute(). When UAC is on and I run it normally under the UAC account everything works and the browser opens. Run with "Run As Administrator" it fails. It's easy to test.
Not sure if this is a bug in the OS, or whether Microsoft deems this as a security 'feature'.
FWIW, some people have mentioned the setting IE as the default browser works, but it doesn't work for me. Basically no links work if I've elevated rights. This has actually broken quite a few administrative applications we use in the back office for administration.
Using Win7 32-bit for 3 months and didn't have problem with developing any .NET-based applications including ASP.NET apps.
Just upgraded my laptop's RAM 3 days ago and switched to 64-bit version of Win7.
When I'm working on installing IIS7 and .NET Framework 3.5 SP1, there's an error about not all features were installed for some unknown reason.
When I try to register ASP.NET using aspnet_regiis -ir in c:\Windows\Microsft.NET\Framework64\v2.0.50727\, a dialog box shows with this error message:
"Operation failed with 0x80070643" and after I close the dialog box, another error message on the console command shows with this message: "An error has occurred: 0x80004005 Unspecified error".
I had the same problem and I did everything found on the internet but nothing was useful
eventually I was able to solve it by using the following:
note: do it on your own risk
Add the following to you registry only if the doesn't exist (in my case they didn't exist):
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_2.0.50727]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_2.0.50727\Names]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_2.0.50727\Performance]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_64]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_64\Names]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_64\Performance]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_64_2.0.50727]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_64_2.0.50727\Names]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_64_2.0.50727\Performance]
try installing asp.net 64 bit after that
Configure IIS to run in 32 bit mode (assuming your apps are 32 bit mode, since that's what you originally developed on).
http://learn.iis.net/page.aspx/201/32-bit-mode-worker-processes/
Try running aspnet_regiis after that is done. Use the 32 bit version of aspnet_regiis.
I know this is a fairly old post, but I thought I'd share what I did to solve this problem on my machine running Windows 7 64-bit.
While IIS was installed on my computer, the ASP.NET features were not enabled.
To enable ASP.NET do the following:
Navigate to the Turn Windows features on or off dialog. It's located under
Control Panel --> Programs and Features.
Note: Typing 'features' in the Start Menu search will also get you there.
When the Turn Windows features on or off dialog appears, navigate to World Wide Web Services --> Application Development Features
and make sure ASP.NET is checked.
Once this was done the aspnet_regiis -ir command worked perfectly and I could run and debug ASP.NET apps on my machine.
Hope this helps.
set IIS to run in 32 bit mode
http://learn.iis.net/page.aspx/201/32-bit-mode-worker-processes/
Try running aspnet_regiis after that is done. Use the 32 bit version of aspnet_regiis.
بریده جراید
I just installed VS2008 on a brand new Win7 machine and have started at a new company. I am now running the company's main project and all is well...except that, for some reason, .Net keeps breaking on some javascript errors. This isn't in the browser (although it only happens when running IE, in this case version 8).
I'm at a loss as to where to find the option to turn off the javascript debugging in VS 2008.
Can anyone point me in the right direction?
The setting is actually in IE.
Tool -> Internet Options -> Advanced
Under browsing
Check Disable Script Debugging.