Visual Studio stop running the application once I start - visual-studio-2013

I'm using MVC5 with C# application but what my problem is VS 2013 and VS 2015 immediately stops whenever I try to run the application. Output window is showing the below message:
The program '[8916] iisexpress.exe: Program Trace' has exited with code 0 (0x0). The program '[8916] iisexpress.exe' has exited with code 0 (0x0).

Related

Visual Studio 2019 (itself): Exception Has Been Thrown By The Target of an Invocation

Last night I installed Visual Studio 2019 Enterprise, installed most of my usual extensions and played around bit, without issue. Shut it down, then this morning when I fired it back up, just after the VS splash screen I get this:
After that, VS just exits. I've tried running VS in /safemode but the same thing happens. After running ProcDump (Procdump64.exe -w devenv.exe -e 1 -n 1000 -f *TargetInvocationException* -ma > out.txt) no .dmp files are created, but the out.txt file shows this:
Waiting for process named devenv.exe...
Process: devenv.exe (10576)
Process image: C:\Coding\IDE\VS2019\Common7\IDE\devenv.exe
CPU threshold: n/a
Performance counter: n/a
Commit threshold: n/a
Threshold seconds: n/a
Hung window check: Disabled
Log debug strings: Disabled
Exception monitor: First Chance+Unhandled
Exception filter: [Includes]
*TargetInvocationException*
[Excludes]
Terminate monitor: Disabled
Cloning type: Disabled
Concurrent limit: n/a
Avoid outage: n/a
Number of dumps: 1000
Dump folder: C:\Downloads\
Dump filename/mask: PROCESSNAME_YYMMDD_HHMMSS
Queue to WER: Disabled
Kill after dump: Disabled
Press Ctrl-C to end monitoring without terminating the process.
[16:33:52] Exception: 04242420
[16:33:53] Exception: E0434352.CLR
[16:33:53] Exception: E0434352.CLR
[16:33:53] Exception: E0434352.CLR
[16:33:53] Exception: E0434352.CLR
[16:33:56] Exception: E0434352.CLR
[16:33:56] Exception: E0434352.CLR
[16:33:56] Exception: E0434352.CLR
[16:33:56] Exception: E0434352.CLR
[16:33:56] Exception: E06D7363.msc
[16:33:56] Exception: E0434352.CLR
[16:33:56] Exception: E0434352.CLR
[16:33:56] Exception: E0434352.CLR
[16:33:56] Exception: E0434352.CLR
[16:33:57] The process has exited.
[16:33:57] Dump count not reached.
I've also tried running sfc /scannow, devenv /updateconfiguration, checking for any new Windows updates, and running VS as Admin, but still stuck at this spot. Until I get this fixed Visual Studio 2019 is useless to me. Anyone know of a solution?
​Well, while I still have no idea what exactly got screwed up, after waiting a while, I decided to try a re-install over the top of the previous installation in hopes of it fixing itself; running the installer showed there's an update to VS 2019 as well as an update to VS 2017, so I updated both and when it was all done vs 2019 was able to start again.
This problem occurred for me after i limited windows UAC settings, and solved by running the VS as Administrator.
Try this.
Open Windows Explorer, and navigate to <Visual Studio Installation Path>\Common7\IDE (by default is C:\Program Files or Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE);
Delete the ItemTemplatesCache, ProjectTemplatesCache folders;
Open Visual Studio Command Prompt under Start menu -> All Programs -> Microsoft Visual Studio -> Visual Studio Tools (run it with administrative privilege);
Run the devenv /InstallVSTemplates switch;
Run the devenv /Setup switch
Just Repair your visual studio 2017

'Failed to halt - Process 1932 has exited with status 0'

I've only recently started experiencing an issue in Visual Studio Code while running applications in debug mode, I always get this error:
Failed to halt - Process 2152 has exited with status 0
Just after main() function exits, even when I import only fmt package and print "Hello World", or running applications those were previously working.
I pulled same project on another machine and run it (for example "Hello World" project). I'm getting the same error message.
Has anyone else experienced the same? It doesn't seem to occur when I run built applications using cmd (command prompt).

Unable to debug .NET Core app

I'm having and issue with Visual Studio and a .NET Core API project. It's been working fine but something must have changed because I'm now getting the following output when trying to debug the project:
The program '[18032] dotnet.exe' has exited with code -2147450749 (0x80008083).
The program '[17688] iisexpress.exe' has exited with code 0 (0x0).
The program '[5500] iexplore.exe' has exited with code -1 (0xffffffff).
The event viewer is showing this error:
Failed to start process with commandline '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\ProjectSystem\VSIISExeLauncher.exe" -debug -p "C:\Program Files (x86)\dotnet\dotnet.exe" -a "C:\Projects\Utilities\API\src\API\bin\Debug\netcoreapp1.0\API.dll" -pidFile "C:\Users\username\AppData\Local\Temp\tmp742C.tmp" -wd "C:\BlueSky\Utilities\API\src\API"', ErrorCode = '0x80004005'.
I'm not sure why this is happening, if anyone has any insight into this it would be appreciated.
Do as fallow:
Close Visual Studio
Delete the project.lock.json file (if exists)
If above step won't help then try to remove .vs folder
Open Visual Studio as Administrator (the file will be restored and you shouldn't have problems anymore)
There is also an option to use Kestrel instead of IIS Express but that's just an workaround.

error MSB3073: The command "call "C:\project\clientdll\dependencies\gitrev.bat" :VCEnd" exited with code 255

I'm getting this message when trying to build my project (Visual Studio 2010):
Error 120 error MSB3073: The command "call "C:\project\clientdll\dependencies\gitrev.bat"
:VCEnd" exited with code 255.
Yes, the file does exist, I used this command in Pre build event, it looks like this:
call "$(SolutionDir)dependencies\gitrev.bat"
Any ideas?
Your Visual Studio is probably not openend with sufficient privileges. Open as admin and try again.
1) right click on Visual Studio Icon
2) choose run as administrator
3) In Start page choose your application.
4) Clean solution
5) Verify if outputs are removed and that the bat file is present in location
6) Rebuild solution
7) Check for errors again.
I had the same error when forgot to add the "call" prefix before the label:
(
...
:MYLABEL blablabla
...
)
The "(:" sequence basically will output the "Continue?" in the opened console window. Seems the Visual Studio does some track of what kind of cmd.exe behaviour and immediately stops the cmd.exe process with the 255 error.
I've had another error like:
error MSB3073: :VCEnd" exited with code -1.
Where the reason of this was the script output of another sequence (only in Visual Studio 2010 and higher):
... error ... :
Well, the Visual Studio tries to guess there the script behaves badly and stops it with these kind of errors.

SDL Event Debug Problem

I am currently trying to get SDL events to work, but problem is that the program is not working.
When I ran the program; it open and closes very quickly, and the debug gave these errors:
The thread 'Win32 Thread' (0xb60) has exited with code 1 (0x1).
The thread 'Win32 Thread' (0xe00) has exited with code 1 (0x1).
The thread 'Win32 Thread' (0x628) has exited with code 1 (0x1).
The program '[868] My Project.exe: Native' has exited with code 1 (0x1).
I am using Visual Studio C++ Express Edition 2008 and the includes files are:
#include "SDL/SDL.h"
#include "SDL/SDL_image.h"
#include &#60windows.h>
#include &#60string>
The code that I'm trying to get working can be found at:
http://lazyfoo.net/SDL_tutorials/lesson04/index.php
That code is trying to load a file name "x.png". If you do not have a proper PNG file with that name in the working directory then the program will exit with an error code of 1.

Resources