VS 2019 always crashes whenever I try to open this one solution

Falanga, Rod, DOH 260

I am tasked with maintaining an old VB.NET ASP.NET WebForms application. It has 9 projects within the solution. It is at least 15 years old, which is longer than I have been employed in this position. None of the original developers are around. They left no documentation. They didn't even put the source code into any version control system.

My PC has been experiencing major issues over the last few months. My desktop support people reimaged the PC. I've done my best to install of the development software I used to have, I believe I've done that correctly.

The original developers worked on this application over many years. They would always use whatever version of Visual Studio and .NET Framework was around, when they worked on it. Consequently, different versions of the .NET Framework starting at version 2 and going to version 4.5.2, are in this application. I asked my boss if I could settle on one .NET Framework, and his answer was a very loud, "NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!".

Now that my machine is reimagined I've tried to open this Visual Studio solution. VS 2019 crashes immediately after I open it, giving this error:

Log Name: Application Source: Application Error Date: 1/10/2025 1:18:14 PM Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords:
User: OURDOMAIN\Rod.Falanga Computer: MYMACHINE.ournetwork.nmsg Description: Faulting application name: devenv.exe, version: 16.11.35425.106, time stamp: 0x671bf495 Faulting module name: KERNELBASE.dll, version: 10.0.22621.4601, time stamp: 0xd05261a4 Exception code: 0xc000041d Fault offset: 0x0014b472 Faulting process id: 0x0x5B48 Faulting application start time: 0x0x1DB639CBA9BAE68 Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\devenv.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 2cf4a8b4-1c69-4719-8ce9-92ddfcfd3933 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2025-01-10T20:18:14.1351851Z" /> <EventRecordID>10632</EventRecordID> <Correlation /> <Execution ProcessID="17772" ThreadID="13852" /> <Channel>Application</Channel> <Computer>MYMACHINE.ournetwork.nmsg</Computer> <Security UserID="S-1-5-21-448539723-413027322-725345543-98862" /> </System> <EventData> <Data Name="AppName">devenv.exe</Data> <Data Name="AppVersion">16.11.35425.106</Data> <Data Name="AppTimeStamp">671bf495</Data> <Data Name="ModuleName">KERNELBASE.dll</Data> <Data Name="ModuleVersion">10.0.22621.4601</Data> <Data Name="ModuleTimeStamp">d05261a4</Data> <Data Name="ExceptionCode">c000041d</Data> <Data Name="FaultingOffset">0014b472</Data> <Data Name="ProcessId">0x5b48</Data> <Data Name="ProcessCreationTime">0x1db639cba9bae68</Data> <Data Name="AppPath">C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\devenv.exe</Data> <Data Name="ModulePath">C:\WINDOWS\System32\KERNELBASE.dll</Data> <Data Name="IntegratorReportId">2cf4a8b4-1c69-4719-8ce9-92ddfcfd3933</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event>

I've submitted this to Microsoft Feedback Hub. I'm sure I'll hear back from them, but that could be weeks or even months later. I need an answer next week. Can anyone help me, please?

Albert Kallal 5,331 Reputation points

2025-01-10T22:18:07.7633333+00:00

As suggested in the other answer, I would try opening one project at a time, not the "main" project that (I assume) has multiple projects. And before you try opening ANY of the projects? Are you able to create a new webforms (.net) project? I would try/test this, as it only takes a minute or 2. If that project can be created + run, then you at least know you have the correct bits and parts installed for a web forms project. Keep in mind that vs2019, or later DOES NOT install the web forms workflows and support. You have to install these additional workflows, and thus my suggesting to test/check/try creating a new project for a 2 minute quick test. And try opening any of the included webforms in design mode - do they work? In other words, it makes little sense to try and load some "monster" project, when a simple basic project can't be created and runs. So, try creating a test project - see if works. If you don't have the templates to create such a project, then as noted, you are missing the webforms workflows and parts for webforms development - they are NOT installed by default into vs2019, but are available from tools->get tools and features.

So, do the above quick test and create of a webforms project - that will tell you if you have the correct workflows installed. And if that works, then as suggested in the other answer here, try opening one project at a time, not the "main" big project with multiple sub projects included (if that is in fact your case here).
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

1 answer

Michael Taylor 56,091 Reputation points

2025-01-10T21:12:28.71+00:00

Firstly, to be clear, your project IS NOT running on multiple frameworks at the same time. There is only 1 CLR loaded into a process and it'll be the version that the app says to use. Everything else, irrelevant of what the project says, runs on that framework. Since CLR v4 it really doesn't matter what specific 4.x version of the framework you target as they will all run on the currently installed version of the CLR v4. There can be only 1 copy of that on a machine. For example your projects may target v4.5, v4.6.1 and even v4.7. But the app project determines the "target" runtime. Suppose that is v4.7.2. Then at runtime that is what is expected to be available. This really doesn't have much impact anymore outside the development environment. Provided the host machine has at least v4.7.2 installed then your app will run fine. If a Windows Update, or user, installs v4.8.1 then that is the version your app runs against. There is nothing you can do about it and it will not really impact anything. So updating the target framework of your projects, outside the app project, has really no noticeable effect.

Of course if you're talking about pre-v4 projects then VS probably won't load them at all because anything prior to v4.0 requires the CLR v2 which was obsolete a decade ago and code targeting that version won't even run in v4, nor would it ever. So there would be no way for that situation to have occurred before anyway.

On to your actual problem. Reporting to MS is the best choice but my guess is that there is something in one of the projects that is causing a failure. Normally the project simply wouldn't load but it is possible to crash VS. To be honest the event log entry doesn't provide anything useful here. Ideally you should run VS with the /log option and then look at the log that it generates. This will provide more useful information. But even with the log it may not help you.

My gut instinct is that the projects are relying on a custom tool or library to load and it isn't available. This is especially common with COM and third party libraries. Still shouldn't crash VS though. I assume you have already confirmed you can create a new VB.NET project with the older target framework?

This is where the first thought comes in. VS does not auto-install all supported frameworks. If you attempt to load a project that uses a framework that isn't installed then VS will pop up a message offering to: install the framework, upgrade the project or unload the project. Generally you upgrade the project but installing the framework would also work provided the framework is supported by VS. Note that VS2019 supports pre-v4 framework code but only if you installed support for it. So if you have pre-v4 code then rerun the VS installer and add support for the older framework.

If that doesn't get you past the error then the next step is to narrow down the problem. You need to unload all the projects and load them back one by one. Since VS won't load the solution then this is going to be difficult so what I'd do is create a brand new empty solution, doesn't matter where. Then copy the solution file (.sln) into your existing solution directory and open it in VS. Once VS loads the empty solution then use Add -> Add Existing Project to add the projects back to the solution one by one. I would recommend doing so in order of dependencies so projects that have no other project dependencies first followed by projects dependent on those loaded next. The app would be the last project. Save after each successful load. Eventually I would expect a project to fail to load and this is where you can start troubleshooting what is going on.
Please sign in to rate this answer.
Falanga, Rod, DOH 260 Reputation points

2025-01-13T17:01:11.38+00:00

Hello Michael, I never knew that a Visual Studio solution, comprised of multiple projects which were all written using different versions of the .NET Framework, would only be built with one version of the .NET Framework. That is complete new to me. This old app is comprised of 9 VB.NET projects, using one of 5 different .NET Frameworks. I had thought that Visual Studio, would build each project using the .NET Framework saved in that project's .vbproj file. So, your assertion is completely new and unexpected, to me.

Then how does Visual Studio decide which is the "target" project? Is it the project that in the solution file is identified as the start project?

I will do as you and Albert recommend, and start a new, empty VB.NET / ASP.NET WebForms project, based on the highest .NET Framework used, then try adding each project to it. It won't be easy, at least concerning the reports, because they wrote it so long ago that the version of Crystal Reports is no longer supported and I'm sure we don't have a license for. And they also used an old version of Excel (I don't know which version) for one of the reports. It will probably take me all week to do this, so I'll get back to you later.

Falanga, Rod, DOH 260 Reputation points

2025-01-13T18:26:11.1766667+00:00

I have just created a new VB.NET project, using .NET Framework 4.5.2, since that seems to be the .NET Framework the original developers used most for the 9 projects they added to the solution. All I've done, is selected the WebForms template with .NET Framework 4.5.2. Then VS 2019 instantly crashed.

Here's what's in the event viewer:

Log Name: Application Source: Application Error Date: 1/13/2025 11:18:11 AM Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords:
User: DOH\Rod.Falanga Computer: MYMACHINE.nmsg Description: Faulting application name: devenv.exe, version: 16.11.35425.106, time stamp: 0x671bf495 Faulting module name: KERNELBASE.dll, version: 10.0.22621.4601, time stamp: 0xd05261a4 Exception code: 0xc000041d Fault offset: 0x0014b472 Faulting process id: 0x0x5294 Faulting application start time: 0x0x1DB65E77E72391A Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\devenv.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: aa778869-9dad-4917-9ed5-a201341a9739 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2025-01-13T18:18:11.5722294Z" /> <EventRecordID>12475</EventRecordID> <Correlation /> <Execution ProcessID="26384" ThreadID="26388" /> <Channel>Application</Channel> <Computer>MYMACHINE.nmsg</Computer> <Security UserID="S-1-5-21-448539723-413027322-725345543-98862" /> </System> <EventData> <Data Name="AppName">devenv.exe</Data> <Data Name="AppVersion">16.11.35425.106</Data> <Data Name="AppTimeStamp">671bf495</Data> <Data Name="ModuleName">KERNELBASE.dll</Data> <Data Name="ModuleVersion">10.0.22621.4601</Data> <Data Name="ModuleTimeStamp">d05261a4</Data> <Data Name="ExceptionCode">c000041d</Data> <Data Name="FaultingOffset">0014b472</Data> <Data Name="ProcessId">0x5294</Data> <Data Name="ProcessCreationTime">0x1db65e77e72391a</Data> <Data Name="AppPath">C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\devenv.exe</Data> <Data Name="ModulePath">C:\WINDOWS\System32\KERNELBASE.dll</Data> <Data Name="IntegratorReportId">aa778869-9dad-4917-9ed5-a201341a9739</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event> I do not think that it's some project that's causing this, because I haven't even had a chance to add one of the existing projects to this solution. And as a reminder, this machine was reimaged less than 3 weeks ago!

So, what in heck is wrong and how do I get it fixed???

Falanga, Rod, DOH 260 Reputation points

2025-01-13T18:29:17.0533333+00:00

Oh, BTW, I have already tried repairing VS 2019 using Visual Studio Installer, to no effect.

Michael Taylor 56,091 Reputation points

2025-01-13T18:42:25.01+00:00

I never said the projects all build to the same framework. Each project builds for the framework it is targeted for. They all RUN against a single framework and that framework is the one that your EXE is targeting. For v4.x projects that is always the CLR v4 version installed on the machine (most likely v4.8.1). Historically the build framework would impact what features were turned on and off for the compiler. But since v4 very little changes as ultimately it is the same runtime. When you start targeting v5 and newer then you'll see bigger differences because the C# language version is tied to the NET Core version you target.

My point was that upgrading a class library from v4.5 to v4.7.2 has no real effect on the runtime behavior because your code is going to run against the target framework of the EXE it is hosted in. Can you clarify whether all your projects are targeting v4.x or higher? What target framework is your EXE project using?

The "Target" project is the executable you are running (e.g. console app, Winforms app, web app, etc). Class libraries cannot be debugged by the debugger directly. The startup project in VS is almost always the executable project. It is shown in bold in Solution Explorer. When you start the debugger that is the project that runs and then it might load your other projects as dependencies.

Does it crash if you create a VB.NET project that is simply a console or Winforms app? The error indicates an exception but doesn't clarify what. Start VS with the /log option (devenv.exe /log Lognameandpath) and then replicate the issue. When it fails open the given log file to see what it says. You don't have to be still using IE are you?

Albert Kallal 5,331 Reputation points

2025-01-13T20:37:41.84+00:00

Ok, so we now know that creating a fresh new webforms (asp.net webforms application, vb.net) DOES NOT work. Hence, it makes ZERO sense to attempt to work on existing projects until such time a simple working project, well, can work!

Without the ability to work on, create a simple basic project, then as noted, we NEVER going to be able to attempt working on some existing projects, right?

So, the ability to create + work on a fresh new project certainly needs to be fixed before ANY additional progress forward and work on the existing projects can even be attempted, considered, or played with, or even I dare say EVEN opened and worked on.

So, as I suggested here, you want to install the additional .net workflows and support for these older projects. And installing VS does NOT by default install the required workflows and components that will allow you to work on such projects.

So you want (need to) make sure the additional parts are installed. So, tools->get tools and features.

You want these extra things - check if you have them installed:

And in fact, I would check box all of the above .net frameworks - since you dealing with all kinds of different frameworks.

And as for the build process with multiple projects? Yes, the MAIN project determines the build framework - not each individual project settings. And this ALSO applies to the CPU settings - again the main project that all child projects will use the main one project settings for this.

However, as I stated, there is clearly a install and setup issue you have. Then again, for the last 10 years, I have NEVER launched VS without choosing run as administrator.

Regardless, you need to try adding the additional parts above, and you NEED to be able to create and run a fresh project before trying to work on existing projects. If you can't create a basic working project from scratch without a crash, then it follows that you not ever going to be able to work on existing projects until such time that opening ANY project and building it is made to work on your computer.

Falanga, Rod, DOH 260 Reputation points

2025-01-13T20:42:47.6566667+00:00

Michael, one of the projects targets .NET Framework 2. The rest are .NET Framework 4 or above to 4.5.2.

Michael Taylor 56,091 Reputation points

2025-01-13T21:29:18.9266667+00:00

In general a v2 assembly won't load in a v4 runtime. They are different environments. However if your web app had useLegacyV2RuntimeActivationPolicy set to true then it would work for compatibility purposes. It was a hack to allow people to migrate to v4 but it caused other issues. Ultimately you'll want to fix this. But the most issue this would cause is VS would say you need to install the v2 framework. It wouldn't prevent VS from loading.

Given that a simple, v4 web app won't load then this isn't causing your issue. Out of curiosity, does creating a C# web app work?

Falanga, Rod, DOH 260 Reputation points

2025-01-14T17:25:40.1933333+00:00

Michael, the VB project that is at .NET Framework 2, happens to be the main webforms project.

I've got the .vbproj file open in VS Code. There is no useLegacyV2RuntimeActivationPolicy property in it. What would the default be, if that property isn't set?

I've run the Visual Studio Installer and made use that I've added .NET Framework 4.8 developers tools and Additional project templates ..., neither of which had been added before. Unfortunately, it hasn't helped. I opened VS 2019, then tried to open the new, empty VS project, but it failed. Here's what's in the event log:

! <Channel>Application</Channel>

<Computer>MYMACHINE.nmsg</Computer>

<Security />

</System>

<EventData>

<Data>Application: devenv.exe ```Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NotSupportedException at Microsoft.VisualStudio.PlatformUI.MultiValueConverter`4[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Convert(System.__Canon, System.__Canon, System.__Canon, System.Object, System.Globalization.CultureInfo) at Microsoft.VisualStudio.PlatformUI.MultiValueConverter`4[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ConvertCore(System.Object[], System.Type, System.Object, System.Globalization.CultureInfo) at Microsoft.VisualStudio.PlatformUI.MultiValueConverterBase`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Convert(System.Object[], System.Type, System.Object, System.Globalization.CultureInfo) at System.Windows.Data.MultiBindingExpression.TransferValue() at System.Windows.Data.MultiBindingExpression.Transfer() at System.Windows.Data.MultiBindingExpression.UpdateTarget(Boolean) at System.Windows.Data.MultiBindingExpression.AttachToContext(Boolean) at System.Windows.Data.MultiBindingExpression.AttachOverride(System.Windows.DependencyObject, System.Windows.DependencyProperty) at System.Windows.Data.BindingExpressionBase.OnAttach(System.Windows.DependencyObject, System.Windows.DependencyProperty) at System.Windows.StyleHelper.GetInstanceValue(System.Windows.UncommonField`1<System.Collections.Specialized.HybridDictionary[]>, System.Windows.DependencyObject, System.Windows.FrameworkElement, System.Windows.FrameworkContentElement, Int32, System.Windows.DependencyProperty, Int32, System.Windows.EffectiveValueEntry ByRef) at System.Windows.FrameworkTemplate.ReceivePropertySet(System.Object, System.Xaml.XamlMember, System.Object, System.Windows.DependencyObject) at System.Windows.FrameworkTemplate+<>c__DisplayClass45_0.<LoadOptimizedTemplateContent>b__3(System.Object, System.Windows.Markup.XamlSetValueEventArgs) at System.Xaml.XamlObjectWriter.OnSetValue(System.Object, System.Xaml.XamlMember, System.Object) at System.Xaml.XamlObjectWriter.Logic_ApplyPropertyValue(MS.Internal.Xaml.Context.ObjectWriterContext, System.Xaml.XamlMember, System.Object, Boolean) at System.Xaml.XamlObjectWriter.Logic_DoAssignmentToParentProperty(MS.Internal.Xaml.Context.ObjectWriterContext) at System.Xaml.XamlObjectWriter.Logic_AssignProvidedValue(MS.Internal.Xaml.Context.ObjectWriterContext) at System.Xaml.XamlObjectWriter.WriteEndObject() at System.Xaml.XamlWriter.WriteNode(System.Xaml.XamlReader) at System.Windows.FrameworkTemplate.LoadTemplateXaml(System.Xaml.XamlReader, System.Xaml.XamlObjectWriter) Exception Info: System.Windows.Markup.XamlParseException at System.Windows.FrameworkTemplate.LoadTemplateXaml(System.Xaml.XamlReader, System.Xaml.XamlObjectWriter) at System.Windows.FrameworkTemplate.LoadTemplateXaml(System.Xaml.XamlObjectWriter) at System.Windows.FrameworkTemplate.LoadOptimizedTemplateContent(System.Windows.DependencyObject, System.Windows.Markup.IComponentConnector, System.Windows.Markup.IStyleConnector, System.Collections.Generic.List`1<System.Windows.DependencyObject>, System.Windows.UncommonField`1<System.Collections.Hashtable>) at System.Windows.FrameworkTemplate.LoadContent(System.Windows.DependencyObject, System.Collections.Generic.List`1<System.Windows.DependencyObject>) at System.Windows.StyleHelper.ApplyTemplateContent(System.Windows.UncommonField`1<System.Collections.Specialized.HybridDictionary[]>, System.Windows.DependencyObject, System.Windows.FrameworkElementFactory, Int32, System.Collections.Specialized.HybridDictionary, System.Windows.FrameworkTemplate) at System.Windows.FrameworkTemplate.ApplyTemplateContent(System.Windows.UncommonField`1<System.Collections.Specialized.HybridDictionary[]>, System.Windows.FrameworkElement) at System.Windows.FrameworkElement.ApplyTemplate() at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Primitives.ToolBarPanel.MeasureGeneratedItems(Boolean, System.Windows.Size, Boolean, Double, System.Windows.Size ByRef, Double ByRef) at System.Windows.Controls.Primitives.ToolBarPanel.MeasureOverride(System.Windows.Size) at Microsoft.VisualStudio.PlatformUI.VsToolBarPanel.MeasureWithCollapsePrevention(System.Windows.Size) at Microsoft.VisualStudio.PlatformUI.VsToolBarPanel.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.DockPanel.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Border.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Grid.MeasureCell(Int32, Boolean) at System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef) at System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean) at System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Control.MeasureOverride(System.Windows.Size) at System.Windows.Controls.ToolBar.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at Microsoft.VisualStudio.PlatformUI.VsToolBarTray.WorkaroundMeasureOverride(System.Windows.Size) at Microsoft.VisualStudio.PlatformUI.VsToolBarTray.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Border.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.DockPanel.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Grid.MeasureCell(Int32, Boolean) at System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef) at System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean) at System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Control.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Grid.MeasureCell(Int32, Boolean) at System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef) at System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean) at System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Window.MeasureOverrideHelper(System.Windows.Size) at System.Windows.Window.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Interop.HwndSource.SetLayoutSize() at System.Windows.Interop.HwndSource.set_RootVisualInternal(System.Windows.Media.Visual) at System.Windows.Interop.HwndSource.set_RootVisual(System.Windows.Media.Visual) at System.Windows.Window.SetRootVisual() at System.Windows.Window.SetRootVisualAndUpdateSTC() at System.Windows.Window.SafeCreateWindowDuringShow() at System.Windows.Window.ShowHelper(System.Object) at System.Windows.Window.Show() at Microsoft.VisualStudio.PlatformUI.GetToCode.QuickStartWindow.OnClosing(System.Object, Microsoft.VisualStudio.PlatformUI.GetToCode.WorkflowHostClosingEventArgs) at System.EventHandler`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Invoke(System.Object, System.__Canon) at Microsoft.VisualStudio.PlatformUI.GetToCode.WorkflowHostViewModel.OnCloseExecuted(Microsoft.VisualStudio.PlatformUI.GetToCode.WorkflowCompletedEventArgs) at Microsoft.VisualStudio.PlatformUI.GetToCode.WorkflowHostViewModel.OnCompleted(System.Object, Microsoft.VisualStudio.PlatformUI.GetToCode.WorkflowCompletedEventArgs) at Microsoft.VisualStudio.PlatformUI.GetToCode.WorkflowHostViewModel+WorkflowDecorator.<AddHandlers>b__36_3(System.Object, Microsoft.VisualStudio.PlatformUI.GetToCode.WorkflowCompletedEventArgs) at System.EventHandler`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Invoke(System.Object, System.__Canon) at Microsoft.VisualStudio.PlatformUI.GetToCode.GetToCodeWorkflowViewModel.OnMruItemOpening(System.Object, Microsoft.VisualStudio.PlatformUI.MruItemOpeningEventArgs) at Microsoft.VisualStudio.PlatformUI.CodeContainerListViewModel.OnOpen(Microsoft.VisualStudio.PlatformUI.CodeContainerViewModelBase) at Microsoft.VisualStudio.PlatformUI.CodeContainerViewModelBase+<>c__DisplayClass68_0.<.ctor>b__0(System.Object) at Microsoft.VisualStudio.PlatformUI.DelegateCommand.Execute(System.Object) at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(System.Windows.Input.ICommandSource, Boolean) at System.Windows.Controls.Primitives.ButtonBase.OnClick() at System.Windows.Controls.Button.OnClick() at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(System.Windows.Input.MouseButtonEventArgs) at System.Windows.UIElement.OnMouseLeftButtonUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs) at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object) at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent) at System.Windows.UIElement.OnMouseUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs) at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object) at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs) at System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs, Boolean) at System.Windows.Input.InputManager.ProcessStagingArea() at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs) at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport) at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32) at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef) at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) </Data> </EventData> </Event> xxxx

Michael Taylor 56,091 Reputation points

2025-01-14T17:35:33.16+00:00

The default is to not use the legacy runtime. That has negative impact on apps and changes the behavior. Most v4 assemblies are not built for that so it could cause compatibility issues.

If it was working before then you were lucky in my opinion. I could understand why your boss would be concerned. I would prioritize upgrading the project to v4. This shouldn't be too bad to be honest. It does impact the server when you deploy to the server as the app pool, if IIS, changes. There are also lots of web config changes to the point that most people recommended creating a new web project in v4 and then moving all the pages/controls/codebehind/etc over one by one, updating the config as you go.

But, as mentioned earlier, this isn't causing your failure because you weren't even able to create a v4 ASPNET project. Can you also go to Tools \ Options and then Web Forms Designer and then switch the Web Live Preview to the legacy designer. Curious if VS is failing to load the designer and it is tanking it.

Michael Taylor 56,091 Reputation points

2025-01-14T17:36:50.6866667+00:00

This error is coming from the designer it looks like. Refer to my earlier comment about disabling Web Live PReview and see if the problem goes away.

Albert Kallal 5,331 Reputation points

2025-01-14T19:04:11.0633333+00:00

I 2nd the suggestion to try using the legacy webforms designer, and NOT the new live preview. So, in tools->options, do down to Web Forms designer, and choose this option:

Once done, then again try creating say a "web forms application", (not web site), and choose .net framework template - not a .net one (which means .net core). See if that project can open. If yes, then you can start trying to open individual projects, and see if they open.

So, after changing above setting, then try this template:
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

VS 2019 always crashes whenever I try to open this one solution

1 answer

Your answer