I have a Visual Studio solution with roughly 90 projects in it (mixture of Windows Forms in C#/VB.NET,WPF and Silverlight stuff). I have a Windows Forms application (C#) as the startup app. I press F5 to start debugging.
When I exit the debugged application by selecting Stop Debugging in Visual Studio or by selecting Exit in the debugged application, Visual Studio continues the compilation of different assemblies. I have seen no pattern in what assemblies are compiled and it doesn't happen every time.
If I press F5 to start a debugging session, why would Visual Studio continue to build assemblies after I have finished debugging?
Maybe those assemblies that are compiled after your application launches do not affect your application and VS wants to launch your application as early as possible?
Have you checked your solution's Configuration Properties ? You can specify there which projects to be built.
Are you using Edit-and-continue? If so, it's rebuilding the edited assemblies.
Related
I have a very large ASP.NET webforms application project, whose file takes time if I run it in Visual Studio in debug mode. Is there any way if a solution is already built to just click the run button and start debug mode without again building the solution in Visual Studio (any version)?
I am running visual studio 2017 community version 15.7.6.
I am running an asp.net web application in debug mode. When I hit the "Stop" button to stop the debugger, it continues to run the program. I have to close Visual Studio completely to get the program to close.
Things I have tried:
Tools -> Options -> Projects and Solutions -> Web Projects -> Stop debugger when browser window is closed is checked.
Enable Edit and Continue under in the .csproj is checked.
I have closed IIS Express in the System Tray.
Running my application using the Visual Studio 2013 debugger produces the correct behavior, so this issue is just with the VS 2017 debugger.
Nothing works in VS 2017 except closing visual studio completely.
Does anyone know what is going on?
Right-click the IIS Express icon in the Notification Area (aka System Tray), then, under "View Site", hover over your web application. In the fly-out menu, choose "Stop Site". That usually works for me.
As far as I know, Visual Studio just does this sometimes and there's not anything you can do about it. If it's happening consistently I would try reinstalling and/or reverting to older versions to see if the issue persists.
I am using visual studio 2008 (32 bit. My machine is 64 bit). I've build an windows forms EXE application. Now I want to attach the process in visual studio so that when I run the EXE from Debug/Release folder of my project it should hit the breakpoints that I've set in my code which is currently opened in visual studio 2008.
I can see there is a process called MyApplicationName.vshost.exe but the attach button is grayed out.
The reason I wnat to debug the EXE is, I want to debug the EXE at run time. I am getting an exception when I run the EXE from Debug/Release folder but when I run through the code I didn't get any exception
Please let me know which process should I attache in VS2008 so that when I run my EXE from Debug/Release folder of my project it should hit the breakpoints that I've set in my code which is currently opened in visual studio 2008.
If you have the source code, I also suggest you debug your app directly, you could use the Exception throw under Debug->Exceptions window which could help you throw the Exception messages.
For host process, if possible, you could disable it under project property:
If you have to use the attach to process, please run VS as the admin, and then attach to your process directly:
In Visual Studio 2015 community when building forms-applications, only when configuration is set to "Debug" and platform to "Any CPU", the generated .exe actually works. ANY OTHER configuration just doesn't run.
If I try to delete the bin-folder it says the folder is used by another program. Still nothing shows on task manager. I have to reboot to terminate it.
This happens even on empty projects so it can't be caused by my horrible coding. I've even reinstalled Visual Studio but no luck.
I need this to work for my installer that doesn't work with "Any CPU"-config.
So how do I get all configurations to work?
Thanks for helping!
When I open any application or start a new application it will build the application but it will not run the application. I have restarted my computer and checked task manager for any processes pertaining to my application. If I run visual studio as administrator the application will run but it will not build automatically even though in the visual studio setting it is set to build and run. However if I copy my application to another computer it builds and runs perfectly fine. I usually use Visual Studio 2010 Professional but I also have Visual Studio 2012. The problem is constant between the two applications. Any suggestions?
Try removing the obj files withing your project directory.