I have been using Visual Studio for quite some time and for the previous projects, I've been building them just fine, and the console window appeared normally. But with my new projects, it just flashes on for a second and then shuts down. I noticed that for the successfully built projects, the name of those projects would appear on the debugging button; but for the unsuccessfully build projects, there was just the word Start. Please help me with this issue. Thank you very much.
Related
When I go to Project Properties/Publish tab this error is being shown I have searched it alot but nothing valuable is found, Thanks in Advance.
Updating Visual Studio should work, if not then Reinstalling Visual Studio will be required.
Windows 7: Go to Add and Remove Programs, find Visual Studio Installer (+year)
and choose 'change'. Once the window opens, click 'modify'
The default update options should be fine, simply click 'Modify'/'update' in the bottom right corner. Your project should be able to open the publish page after it finishes.
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 having a strange issue and am not sure how to figure out what is happening. I am developing an Add-In for Revit to display a web page in the dock panels. I followed the tutorial here for using GeckoFx45 in WPF. Everything works fine while I am debugging with Visual Studio. If I quit debugging and run the same dll disconnected from Visual Studio, GeckoFx45 stops at Xpcom.Initialize("Firefox");
I haven't recompiled, just running without Visual Studio attached and debugging. Since it works while debugging, I'm not sure how to figure out what is wrong.
If it makes a difference, I am using the most recent GeckoFx45 64 bit NuGet. https://www.nuget.org/packages/Geckofx45.64/
I'm a PHP developer, but recently I have to work with Visual Studio in a C# application. I don't know much about C#, just had a few experiences with it, and the problem is when I try to run/debug my code it works only for the first time. If I change ANY piece of code anywhere in the code the project won't launch anymore, all it does when I click "Debug" is open Google Chrome for me and there it hangs awaiting for "localhost" forever... This issue is driving me nuts, I can't program well if I have to restart Visual Studio whenever I change some code.
I have tried a lot of things that I found here and on Google, but nothing helped. I have fully repaired VS 2015, didn't work. Then I reinstalled it and still not working.
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.