I had no major problems with Visual Studio 2013 (or any VS version all the way back to VS6), but 2015 crashes or hangs several times a day. I've ran it on two different machines, fresh Windows 10 installs with the same crashes on both.
EDIT: This question originally referred to VS 2015 Update 2, but I've edited it several times as each update has been released.
There are many different crashes and hangs and other errors. The most common one as of September 2016 is this:
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at Microsoft.VisualStudio.Shell.ThreadHelper.GetInvoker()
at Microsoft.VisualStudio.Shell.ThreadHelper.InvokeOnUIThread(Microsoft.VisualStudio.Shell.InvokableBase)
at Microsoft.VisualStudio.Shell.ThreadHelper.Invoke(System.Action)
at Microsoft.VisualStudio.Shell.ThreadHelper+<>c__DisplayClass23_0+<<InvokeAsync>b__0>d.MoveNext()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.VisualStudio.Shell.ThreadHelper+<InvokeAsync>d__23.MoveNext()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.VisualStudio.Services.TaskSchedulerService.VsUIThreadScheduler+<ExecuteTaskInRPCPriority>d__3.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_1(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
The crashes occur at random times. Starting a build, resuming after breaking, changing from debug to release, hitting Save All, switching files, even when idle.
Update:
I've given up. VS 2015 is just an embarrassing mess. Between the crashes and other broken features (such as Edit & Continue, broken debugger, breakpoints failing etc. etc.) it is close to unusable for any serious sized C++ project. I've gone back to VS 2013 which runs faster and is far more reliable.
Related
I am attempting to install Visual Studio 2022 Build tools on a fully updated Windows Server 2022 Core installation as a virtual machine on ESXi. Whenever I start the setup, I see the GUI appear while it's extracting files and then it crashes leaving an event log entry:
Application: vs_setup_bootstrapper.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NotImplementedException
at MS.Win32.UnsafeNativeMethods+ITfThreadMgr.CreateDocumentMgr(ITfDocumentMgr ByRef)
at System.Windows.Input.TextServicesContext.RegisterTextStore(System.Windows.Input.DefaultTextStore)
at System.Windows.Input.DefaultTextStore.get_Current()
at System.Windows.Input.TextServicesContext.SetFocusOnDefaultTextStore()
at System.Windows.Input.InputMethod.EnableOrDisableInputMethod(Boolean)
at System.Windows.Input.TextServicesManager.Focus(System.Windows.DependencyObject)
at System.Windows.Input.KeyboardDevice.ChangeFocus(System.Windows.DependencyObject, Int32)
at System.Windows.Input.KeyboardDevice.TryChangeFocus(System.Windows.DependencyObject, System.Windows.Input.IKeyboardInputProvider, Boolean, Boolean, Boolean)
at System.Windows.Input.KeyboardDevice.Focus(System.Windows.DependencyObject, Boolean, Boolean, Boolean)
at System.Windows.Input.KeyboardDevice.Focus(System.Windows.IInputElement)
I have also tried manually extracting the files and running but the same thing happens using this guide because the installer itself is crashing:
https://silentinstallhq.com/visual-studio-build-tools-2022-silent-install-how-to-guide/
Can anyone advise why it's failing?
Installation of Visual Studio Build Tools 2022 on Windows Server 2022 Core will always fail as the Visual Studio Build Tools 2022 will only identify the 2016 and 2019 versions of Windows Server Core as installation candidates, even if a silent installation is requested. The installer will attempt to throw a GUI exception (which Core cannot handle).
The only method for running Visual Studio Build Tools 2022 on Windows Server Core is by doing so on versions 2016 or 2019. Microsoft calls this out specifically in their documentation (from: https://learn.microsoft.com/en-us/visualstudio/releases/2022/system-requirements#microsoft-visual-studio-build-tools-2022-system-requirements):
It is better to use vs in linux.
You can use a VM to do that.
I'm using Visual Studio 2015 to debug a website running on a .NET framework. When setting break points in one of my .aspx.vb files it gives me an error saying:
"The break point will not be hit. No symbols have been loaded for this document."
Now I have solved how to fix this error by going to Debug -> Attach to Process then attaching it to the process of my IIS.
The issue is I have to do this every time I stop and restart debug mode. Is there anyway to get this process to automatically attach when I begin debugging?
The ReAttach extension gives you an easy way to ReAttaching your prior debug targets.
I am working on a project, when I deployed my project to a windows 7 workstation I am prompted with this error message. Any help is very well appreciated.. Thank you
Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click QUIT, the application will close prematurely.
An error occured creating the form. See Exception.InnerException for details. The error is: Method not found: 'Void CrystalDecisions.Windows.Forms.CrystalReportViewer.set_SHowCopyButton(Boolean)'.
If you're making a report for a 32-bit machine, you should try using the 32-bit version of the software. There could be some incompatibilities between the two which is a frequent issue when sharing files between 32-bit and 64-bit applications. This isn't to say it's the only possible issue, but it's a decent guess anyway.
You could also make sure that you have all dependencies for CR installed. Things like Visual studios redistributables and VB\C++ redistributables. Also, make sure that all of the dependencies are 32-bit, although my understanding is this occurring on the 32-bit machine anyway.
I just started developing for Windows 8 store. Even though I open a sample project and start debugging it displays this error.
An unhandled exception of type System.Exception occurred in Unknown Module.
Activation of the Windows Store app 'a9c71d52-8ba1-460a-aa8f-df5ea89f1efa_qpttb2q7b6s4m!App' failed with error The app didn't start.
The program '[2520] App8.exe: Managed (v4.0.30319)' has exited with code -532462766 (0xe0434352).
I have tried to remove references and adding them but they aren't happening. Kindly help me with this weird problem.
After lot of searching and not able to get an answer. I reinstalled Windows 8 and with a new version of VisualStudio everything is in rhythm now.
How do I disable the background compiler for Visual Basic in Visual Studio 2008?
For my sins, I have to work on a large VB.NET project and it often locks up for 20 seconds at a time whilst doing the very helpful background compilation which is extremely frustrating.
I'd rather work blind between compiles and be able to do some work.
No there is no way to disable the background compiler.
Have you installed Visual Studio 2008 SP1. There were several bugs we fixed in the RTM version of VS 2008 which can cause the IDE to hang under certain circumstances.
We take issues with the background compiler very seriously. If you can give us a repro of the problem it will definitely be investigated. If you can produce such a repro or even send us a memory dump when the IDE is locked please file a bug on Connect: https://connect.microsoft.com/VisualStudio
A couple of other steps you can take. Do you have any Add-ins installed in VS? If so try uninstalling them 1 at a time. I've seen several cases where 3rd party add-ins caused lock ups in the IDE which were completely unrelated to the C#/VB framework.