One of our developers is experiencing a system Warning popup when he tries to launch a solution in VS2017. all was working well before today
"devenv.exe - System Warning
Unknown Hard Error"
VS shuts down, whether he presses ok or not and MSBuilds.exe are left in task manager
We tried:
- repairing VS2017
- un-install-restart-reinstall VS2017
Had to remove all .NET components from the machine and re-install em - got it working. Very close to rebuilding the PC
Related
EDIT: Good information provided below to diagnose, but the issue was I was running Visual Studio 2022 17.3. Version 17.4 is required for .NET 7, and I had just installed that. Once I installed the latest version of VS, all my problems went away. Install with Visual Studio
Suddenly today, debugging my ASP.NET Core 6 and 7 apps suddenly has stopped working. I hit F5 to debug, it stops on my breakpoint, but as soon as I continue or step into, I'm shown this dialog:
I haven't made any changes to code, I'm simply trying to continue after I've stopped at a breakpoint. This just started happening today and I can't figure out what I did.
I haven't made any changes to code, I'm simply trying to continue
after I've stopped at a breakpoint. This just started happening today
and I can't figure out what I did.
Well, if your visual studio stop working for debugging all type of application, please check following configuration:
1. Tools > Options > Debugging > .NET/C++ Hot Reload
2. Tools > Options > Projects and Solutions > ASP.NET Core >
Furthermore, If you select the Always rebuild option in the dialog box, you won't see the dialog box again in the current Visual Studio session, and Visual Studio will automatically rebuild and reload instead of showing the dialog box.
Note:
In addition, as you can see above in the first release of Visual Studio (version 17.0) the standard Edit and Continue dialog is still shown when using Hot Reload with the debugger. This was a bug and has been resolved starting with 17.1 Preview 2 release.
If you still need more details about the issue you are having with, I would higly recommend you to check our official document here.
If issue still perist:
After checking above configuration, if your issue still persists and if you are not using Visual Studio (version 17.0) then you still reset your unknown setting in visual studio as following:
Go to Tools > Import and Export Settings.
Then No, just reset settings
Finally, restart Visual studio.
You can get more details here.
When I open a solution in VS 2022, I get the following error.
Task Failed - Activating language client IntelliCode suggestions: IntelliCode suggestions failed to start. The initialization error was logged and will be reported to the IntelliCode team.
I'll post the fix that worked for me.
Make sure VS IDE is closed. Open the Visual Studio Installer and repair the VS IDE where the Intellicode failed to start.
Restart PC after the repair has completed.
This is the only way I could get it to work again. Either that or a complete re-install. I've chosen to repair instead of a complete re-install.
Hope this helps
Yesterday, I could work with Visual Studio 2010 without any problem. However, today after I turned on the computer and tried to open my project (Web application with Visual Basic.NET) on VS2010 again, I got a message box showing as below:
Later, I found out after I tried deleting suo file that this message box will show up whenever I open some file in Visual Studio so I tried to run the application. Then, I found another message box popped up as below:
And after I close the message box, I finally got this window
It says:
Compilation Error
Compiler Error Message: The compiler failed with error code -1073741511.
I have searched for the solution through the internet. I have found a few methods that might solve the solution such as scanning for virus, using clean boot. I have also tried repairing and uninstalling VS2010 and .NET framework but none still work. Right now, I have no idea what I should to do make it work again.
Anyway, I realized that there is Windows auto update when I turned off the computer. Not so sure if this related to the problem (I used Window 8.1).
After formatting Drive C to reinstalling everything again, I found out that the reason might be Windows update. I have started from reinstalling Windows 8, all necessary programs (except Visual Studio and SQL Management Studio) and all window updates required for upgrading to Windows 8.1.
When I successfully got to Windows 8.1, I created system restore point and try installing VS2010 and all windows update. The result had caused the same error I posted in this thread.
After that, I restored back to original state and installed VS2010 first. Then installed some of windows updates. This time, I decided to install all updates except the ones that have publish date after 10/11/2015. The result is satisfied. I don't get this error again.
Later, Hans Passant help me find the actual cause of this problem. Please see this link:
Why do I get an error for "__CrtGetFileInformationByHandleEx " when I try to compile
with VS 2015 Enterprise i get always following message on a solution while debugging: XAML Visual Diagnostic is either disabled or is not supported by the current application
Tools - Options - Debugging - General:
Enable UI Debugging Tools for XAML is enabled
Preview selected elements in Live Visual Tree is enabled
I have tried:
VS Restart
Clean Solution / Rebuild
Fresh Checkout
Curious: If i start the solution without debugging and i attach the debugger to the process, it works ...
Update:
If i select "Enable native code debugging" in project settings - debug, it works !
I needed an additional debugging option to be disabled in order for the tools to work with my projects:
Tools - Options - Debugging - General:
Use Managed Compatibility Mode --> disabled
I also faced this problem for some WPF projects that came to my pc from various sources. In my case the problem was in the project target framework - it was set to .NET Framework 3.5. The Live Visual Tree and the Live Property Explorer in VS 2015 do not work with .NET 3.5:
Inspect XAML properties while debugging
https://msdn.microsoft.com/en-us/library/mt270227.aspx
So I just changed the target framework to .NET Framework 4.0 in the project properties dialog (the Application tab) to make these 'live' tools work.
I faced the save issue on VS 2019. It happened all of a sudden on a project which it used to work on. Restarting VS did not help. But it got resolved after PC restart.
If you're having that problem in VS 2017 while debugging on a remote machine, installing the Visual C++ 2017 Redistributable (x64 in my case) made UI debugging work.
I always had this VM where UI debugging worked but my colleagues couldn't get it to work on their machines until I was experimenting with something where I had to uninstall all redistributables. After finishing my experiments I realized I couldn't debug the UI anymore. I reinstalled the 2017 redistributable and the functionality got enabled again.
I would like to run a .exe file made with visual studio 2003 but I get an error every time I run it on a windows 7 machine, vista machine, and xp machine. The error on Windows 7 and vista says "application has stopped working" and then makes me close the error box.
In windows xp it's a little different error, "the application failed to operate (0xc0000135) Click on OK to terminate the application."
That error code seems to indicate the application failed to initialize correctly.
It is possible that the anticipated .NET version is not present.
As far as I know, VS 2003 by default compiles against the .NET 1.1 library. There is no straightforward way of installing this on a Windows 7 or Vista box. Do you need to compile it against the .NET 1.1 library, or can you load it in VS2005, change the output .net version to 2.0 or higher, and recompile the application?
If you have the source code to the application, try running the application in debug mode and stepping through line by line until you find the exception. If you do not have the source code, possibly try running the application in a couple different compatibility modes. Another option to try is to check the windows event log for anything more specific.
If you want to get really deep into it, you can use SysInternals ProcMon.exe and filter on the failing exe to view the WinAPI calls that are happening during the failure.
Also, a basic search of forums shows that error is usually accompanied with framework issues. Either recompile the application or check out what your required framework is in the VS2003 project settings.