Troubleshooting
In case Visual Studio decides not to show the new templates try this:
For Visual Studio 2017 and 2019, open the VS command line and run:
>devenv /installVSTemplates
For Visual Studio 2022, open the VS command line and run:
>devenv /updateConfiguration
If it still doesn't work, check if the \Wisej 2 or \Wisej 3 templates are present on your development machine under your user name here:
⚠
Documents\Visual Studio (2019|2022)\Templates\ProjectTemplates\Visual C#
Documents\Visual Studio (2019|2022)\Templates\ProjectTemplates\Visual Basic
In case the project templates (or item templates) for Wisej are missing, either run the installer again and select Repair, or download the templates below.
Unblock the zip (this is important!) and expand into:
Documents\Visual Studio (2019|2022)\Templates
Select to overwrite existing files when asked. The zip archives contain the \ItemTemplates and \ProjectTemplates files in the same structure expected by Visual Studio.
Run the >devenv command above again.
👉
If it still doesn't work, delete the Visual Studio templates cache. Each installation of Visual Studio has a different unique ID. Visual Studio 2019 versions start with "16.0" and Visual Studio 2022 versions start with "17.0".
⚠
>dir %LOCALAPPDATA%\Microsoft\VisualStudio
>del %LOCALAPPDATA%\Microsoft\VisualStudio\{version}\ItemTemplatesCache_{00000000-0000-0000-0000-000000000000}
>del %LOCALAPPDATA%\Microsoft\VisualStudio\{version}\ProjectTemplatesCache_{00000000-0000-0000-0000-000000000000}
Run the >devenv command above again.
👉
Occasionally you may start getting designer errors when opening a container in design mode. The most common error is "Unable to cast type..." It's a well-known issue related to Visual Studio having to load a shadow copy of the assemblies used at design time.
Since assemblies cannot be unloaded in .NET Framework, Visual Studio loads shadow copies of the assemblies loaded by the designer. Sometimes it ends up loading the same assembly multiple times, leading to the "Unable to cast" error because the same type is loaded more than once.
Usually it's enough to:
- 1.Close all designer tabs
- 2.Close all Visual Studio instances
- 3.Delete /bin, /obj, /.vs
- 4.Open Visual Studio and reload the solution
- 5.Recompile
If you still get the problem, try to clean the designer assembly cache and repeat the steps above.
⚠
Visual Studio makes shadow copies of the assemblies loaded by the designer here:
%LOCALAPPDATA%\Microsoft\VisualStudio{version}\Designer\ShadowCache
Each installation of Visual Studio has a a different unique ID. Visual Studio 2019 versions start with "16.0" and Visual Studio 2022 versions start with "17.0".
>dir %LOCALAPPDATA%\Microsoft\VisualStudio
>del %LOCALAPPDATA%\Microsoft\VisualStudio\{version}\Designer\ShadowCache
Reopen Visual Studio, recompile again and the problem should be solved.
⚠
Last modified 10mo ago