Add ability to customise Winforms Designer Shadow Cache behaviour about winforms HOT 2 OPEN

@IrisPeter Could you please confirm the TargetFramework of the project - is it targeting .NET or .NET Framework? If it is targeting .NET Framework, are you using any project property which is causing out-of-process designer to be used?
Perhaps sharing your project file contents will help.

Also, is it feasible to use IsAncestorSiteInDesignMode property check around the code which tries to connect to the database? If the code is running in design mode, then probably it doesn't need to connect to the database and hence doesn't require the missing files?

from winforms.

Hi @Shyam-Gupta

The TargetFramework is .NET Framework 4.8

The situation is is that if the <UseWinFormsOutOfProcDesigner>True</UseWinFormsOutOfProcDesigner> setting has not been generated by Visual Studio, and you double click on certain forms, such as a new blank form. Then the designer loads OK, and its only when you click on a certain number of our Forms that Visual Studio then trigger the prompt to use the Out of Forms designer.

The moment the UseWinFormsOutOfProcDesigner flag has been set to true, then even a blank form will cause the login code to run.

Unfortunately there is no C# call stack to trace back to when the code is triggered, this is because the product is a mix of C, C++ and C# code and one of the Managed C++ components, triggers the standard C++ DLL with the login code in it.

In the login component I added an assert for when it discovers that it is running under Visual Studio that I can get any sort of call stack before VS2022 times out.

What kind of do I need to look for in the C# to wrap in this IsAncestorSiteInDesignMode test?

The next item in our call stack is the _DllMainCRTStartup of our C++ DLL

from winforms.