What causes error "Can't resolve types until ITypeIdentityResolutionService has started processing enqueued assemblies."

Question

What causes error "Can't resolve types until ITypeIdentityResolutionService has started processing enqueued assemblies."

Michael Heider - SKIDATA 0

I am using VS2022 version 17.8.0. I have async loading of solution enabled.

I do not use a special winforms designer, it is the designer that comes with the installation of VS2022.

Here is the call stack of the error: Microsoft.DotNet.DesignTools.Client.CodeDom.CodeDomManager.d__11.MoveNext()--- End of stack trace from previous location where exception was thrown ---at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)at Microsoft.DotNet.DesignTools.Client.CodeDom.CodeDomManager.d__10.MoveNext()--- End of stack trace from previous location where exception was thrown ---at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)at Microsoft.DotNet.DesignTools.Client.Loader.VsDesignerLoader.d__59.MoveNext()--- End of stack trace from previous location where exception was thrown ---at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)at Microsoft.DotNet.DesignTools.Client.Loader.VsDesignerLoader.<>c__DisplayClass57_0.<b__1>d.MoveNext()|Instances of this error (1)

Michael Heider - SKIDATA 0 Reputation points

2024-02-29T16:29:14.15+00:00

I am using VS2022 version 17.8.0. I have async loading of solution enabled.

I do not use a special winforms designer, it is the designer that comes with the installation of VS2022.

Here is the call stack of the error:

Microsoft.DotNet.DesignTools.Client.CodeDom.CodeDomManager.d__11.MoveNext()---
End of stack trace from previous location where exception was thrown ---at
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)at
Microsoft.DotNet.DesignTools.Client.CodeDom.CodeDomManager.d__10.MoveNext()---
End of stack trace from previous location where exception was thrown ---at
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)at
Microsoft.DotNet.DesignTools.Client.Loader.VsDesignerLoader.d__59.MoveNext()---
End of stack trace from previous location where exception was thrown ---at
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)at
Microsoft.DotNet.DesignTools.Client.Loader.VsDesignerLoader.<>c__DisplayClass57_0.<b__1>d.MoveNext()|Instances of this error (1)
Michael Taylor 60,326 Reputation points

2024-02-29T16:39:45.33+00:00

Disable async solution loading and see if the problem goes away.

In either case you should use Report a Problem to send a diagnostic request to MS so they can have someone look at it. It is possible a regression issue has occurred. A quick search on this in Developer Community indicates that as late as Mar of this year regression issues had been occurring.

1 answer

Your answer

Michael Heider - SKIDATA 0 Reputation points

2024-02-29T16:29:14.15+00:00

I am using VS2022 version 17.8.0. I have async loading of solution enabled.

I do not use a special winforms designer, it is the designer that comes with the installation of VS2022.

Here is the call stack of the error:

Microsoft.DotNet.DesignTools.Client.CodeDom.CodeDomManager.d__11.MoveNext()---
End of stack trace from previous location where exception was thrown ---at
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)at
Microsoft.DotNet.DesignTools.Client.CodeDom.CodeDomManager.d__10.MoveNext()---
End of stack trace from previous location where exception was thrown ---at
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)at
Microsoft.DotNet.DesignTools.Client.Loader.VsDesignerLoader.d__59.MoveNext()---
End of stack trace from previous location where exception was thrown ---at
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)at
Microsoft.DotNet.DesignTools.Client.Loader.VsDesignerLoader.<>c__DisplayClass57_0.<b__1>d.MoveNext()|Instances of this error (1)
Michael Taylor 60,326 Reputation points

2024-02-29T16:39:45.33+00:00

Disable async solution loading and see if the problem goes away.

In either case you should use Report a Problem to send a diagnostic request to MS so they can have someone look at it. It is possible a regression issue has occurred. A quick search on this in Developer Community indicates that as late as Mar of this year regression issues had been occurring.

Answer 1

Michael Taylor 60,326

You really haven't provided us any context as to what you're trying to do such that this error occurs. Are you trying to open a solution in VS, compile your code, run your app, what?

Just off the top of my head it looks like a VS issue opening the designer. In that case try closing the designer and reopening it. If this is a VS issue then please also confirm the version of VS you're using, What designer (if any) you're trying to load, and whether you have the async solution load option set (in options).

Michael Heider - SKIDATA 0 Reputation points

2024-02-29T15:31:05.1466667+00:00

Your assumption is correct, I tried to open a WinForms Form with the designer in VS2022.
Michael Taylor 60,326 Reputation points

2024-02-29T15:43:01.0533333+00:00

Please reply to answers using the comment button so your responses are tied to the answers. Thanks.

The error you get should only be happening if you are trying to load the designer while the solution is still loading. You could simply close and reopen the designer to work around this. Alternatively you could disable async solution loading but this is not recommended. If you have to go that route then I'd recommend using Report a Problem and send MS the repro case so they can look at it.

My gut instinct is that you might be loading a control (third party?) that has a designer that either doesn't work with the new async process or that doesn't play well with the new winforms designer. You should check in the options to see if you're using the new designer (for NET Framework) and try disabling it to see if the problem goes away.
John Jegla 0 Reputation points

2024-02-29T16:30:51.79+00:00
This is happening to me, too!

It started with an upgrade to 17.9.0, and persists after a further upgrade to 17.9.2.

The error displays after 20-30 seconds of waiting while the forms designer claims to be opening.

It happens when trying to open any Windows Forms form in an existing VS2022 session as well as for any form design windows that were open when starting a new VS2022 session.
John Jegla 0 Reputation points

2024-02-29T16:34:07.8133333+00:00
For me, waiting a while (for the solution to finish loading) and then trying again makes no difference - same error. And:

this error also occurs for very simple forms with no 3rd-party controls

this error also occurs when trying to create a new form (which has no controls at all!)

this error occurs both with-and-without using the new preview out-of-process designer
John Jegla 0 Reputation points

2024-02-29T16:37:13.9266667+00:00

Oh, and deleting the .vs sub-folder of the solution folder does not help - the error still occurs.
Tianyu Sun-MSFT 34,441 Reputation points Microsoft External Staff

2024-03-01T06:37:57.3533333+00:00

Hi @Michael Heider - SKIDATA, @John Jegla ,

Probably it’s a potential issue. The designer failed to load correctly.

Have you tried to reopen your solution(File > Close Solution > click to open it again). If it works, I think this is a temporarily workaround, though the next time you open the solution or create a new solution the same error may still occur.

Please kindly submit a thread on our Developer Community and attach the error message for further investigation.
John Jegla 0 Reputation points

2024-03-09T20:46:08.2266667+00:00
SOLVED!

Although I had unchecked the "Use the preview Windows Forms out-of-process designer..." option in "Tools|Options|Preview Features", that option WAS STILL ENABLED in my project file, separately in EACH build configuration:

<UseWinFormsOutOfProcDesigner>True</UseWinFormsOutOfProcDesigner>

Once I changed all of these values to "False" and reopened the solution, my forms all loaded correctly (although one complicated form no longer displays correctly in the desiger (TabPage Text is missing), but does display correctly at runtime).

So, it seems that there may be a bug in Visual Studio related to synchronizing the project file with at least one of the new preview features...

Share via

What causes error "Can't resolve types until ITypeIdentityResolutionService has started processing enqueued assemblies."

Here is the call stack of the error:

1 answer

Your answer