I want to use iis express with vs 2010 but i can't install sp1 for now, i have figured out how to do this, it is close to this guide How to configure Visual Studio 2008 to use IIS Express? and it works.
My problem is that when vs runs iisexpress it has also an annoying command window (besides the tray icon) which i would like to get rid off.
I can't install sp1 for vs 2010 but i have installed vs 2010 express with sp1 and double checked that when the integrated iis express option is used it runs without command window
First thing i've done was to check if iis express has some command line options to hide the window, but no luck, on the other site option integrated in sp1 can run without this windows, so...
how to do this the same way / or how the sp1 option is doing this ?
p.s. There is however one catch, if vs runs iis express and you wait couple of seconds and then go to tray-> choose website and click Stop Site the command window disappears but iis still runs and the site also, i don't know if this is a bug or something, but then it is like in sp1 no window, only tray icon.
There is no command line option to disable command window, but you can use /systray command line option to disable tray icon.
Visual Studio uses CreateProcess API (or similar API) with creation flag set to CREATE_NO_WINDOW (0x08000000). Following links may help you!
http://msdn.microsoft.com/en-us/library/ms682425(VS.85).aspx
http://msdn.microsoft.com/en-us/library/ms684863(VS.85).aspx
Your observation is due to the fact that VS has attached to iisexpress.exe (when you stopped site from tray icon, iisexpress is in the process of shutdown by closing it's console window etc..., but since VS is attached to it, iisexpress is not able to exit and running in the background and waiting for VS to release)
Related
All of a sudden after I installed Microsoft Edge on Windows 10 gd, Visual Studio is using IIS Express when debugging a web application and it is messing up everything.
How do I get back to normal, so that stupid IISExpress is not used anymore?
Go to the project settings and on the web tab is a drop down that allows you to choose which engine to use.
I went to Project > Properties > Startup Project and then set my start up projects to start the services I need and my project. This reverted my button back to just "Start".
I am having an issue with Visual Studio 2017 RC where when I run an MVC and/or WebAPI app using IIS Express the app never actually runs. Instead I get stuck with a page in the browser indicating it is trying to attach and from there it goes no further. If I open another tab/window in the browser and try to navigate directly to the launch URL, it just spins forever. Likewise when I run this using the dot net run command, the app launches and runs fine.
There do not seem to be any errors that I can see, just that the browser spins indefinitely without actually ever loading the page/endpoint.
Note: this occurs for most any circumstance. Newly created project in VS with no changes, known working project from previous versions, etc.
You could follow or upvote the issue: https://developercommunity.visualstudio.com/content/problem/11391/aspnet-core-iis-express-httplocalhost51733-failed.html
Looks like our workarounds meanwhile are
dotnet run
Publish to local IIS. Which is working for me.
(Untested: downgrade from core-1.1 to core-1.0)
If you aren't familiar with VS2017/asp.net:
You have, or can reveal via View Menu-->Other Toolbars :
Debug toolbar --> dropdowncombobutton saying "[green arrow>] IIS Express"
Click on the dropdown downarrow part of the button.
You should see a Run {yourprojectname} option.
This is the equivalent of dotnet run {yourprojectname} from the commandline.
You can configure the options that appear in the dropdown with
Right-click on project in solution explorer --> Properties --> Debug
I had this same issue and after digging around for a while I discovered that I had dotnet preview v1.0.0-preview2 installed under Programs Files (x86) and a non-preview version in x64. I think VS is launching the x86 (preview) version but expecting to see the full version. To fix this, I did the following.
from programs and feature uninstall every visible dotnet core. (note: for me this did not remove the x86 preview)
go to https://www.microsoft.com/net/download/core#/sdk and install BOTH x86 and x64 SDK packages
open command line and from the root directory check run: dotnet --version (at the time of writing it was 1.0.4)
fire up .net core project in VS 2017 and run.
When I did all of the above, I was able to start up the site in IIS Express from VS.
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.
I'm trying to debug an ASP.NET 3.5 app, which I've recently migrated from VS 2005. (This uses Crystal Reports 11 Release 2, but I don't know if that comes into what's causing me problems, or not.) This app uses Active Directory for authentication. I'll have the app opened in VS 2008, and then press the F5 key to start debugging. Shortly after that VS 2010's Just-In-Time debugger pops up and asked me if I want to (a) debug w3wp.exe, of (b) cancel debugging.
Huh? Why is VS 2010 coming up at all? I don't have it running. I'm not in it. I didn't press F5 in VS 2010. I am in VS 2008 and press Run/Debug there. What's going on; why is VS 2010 interferring?
Edit: Sorry I had to edit my answer. It turned out to be a little more complicated when two versions of VS are involved. Hopefully this edit is more accurate.
If you go to Tools > Options > Debugging > Just-in Time you can enable/disable JIT debugging for the specific version of VS. If you enable more than one VS as JIT debugger, you get to pick between them or set one of them as a default when the VS Jit Debugger is launched. I assume VS2010 replaced your VS2008 JIT debugger during install, so to re-enable it you need to launch VS2008 and go to the menu and enable it. I had to disable and then enable it to get it to work.
If you have set some other debugger, e.g. WinDbg as your JIT debugger, it is a matter of changing the following registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger to point to the desired debugger. Please note that if you run 64 bit Windows there's a shadow entry as well in the Wow64 section. This guide has additional details.
So, I am using visual studio 2005 (and team explorer 2005) with tfs 2008. I have installed both Visual Studio 2005 SP1 and VS80sp1-KB932544-X86-ENU.exe.
I perform the following steps:
Select Project->ASP.NET Configuration within Visual Studio 2005.
Within Visual Studio 2005, attempt to perform either a check-in or a checkout.
The following happens:
The local server started by Visual Studio starts closing itself. I suspect it is crashing; the systray icons are not properly disposed of. It then reopens itself. It does this over and over again, maybe once every second or two. The TFS progress meter doesn't even budge, it just sits there. Canceling out of the checkout does not work; it says it is cancelling and does nothing.
Any suggestions?
So you're trying to make a change in the ASP.NET configuration, then check it in? Or are you talking about checking anything in when it's open? When you say "local server started by Visual Studio", are you talking about the local development server (cassini)? Maybe TFS is trying to save/access something it is using, causing it to crash.
Have you tried stopping all instances of the dev server before checking stuff in/out?