Running WiseJ 2.2 in Visual Studio 2022

0
0

I followed instructions outlined in an earlier question to get WiseJ 2.2 running with Visual Studio 2022.  Everything worked except for Project Templates (oddly enough Item Templates show up fine).  I extracted the specified file and copied the \Templates\ProjectTemplates\Visual Basic\Wisej 2 folder to C:\Users\{MYUSERNAME}\Documents\Visual Studio 2022\Templates\ProjectTemplates\Visual Basic.

However, when I bring up Visual Studio “Create a new project” dialog, nothing with Wisej shows up in the list – image.

I did the same with C# templates and those don’t show up either.  However, everything with Item Templates shows up fine – when I want to add something to an existing WiseJ 2.2.x project.

What am I missing?

 

 

  • You must to post comments
0
0

Actually, based on further inspection of the templates, I think you will need 2 separate sets of them.  One for WiseJ 2.2 and another for 2.5.

If you look inside the VS2022 WiseJ2 Web Application template, specifically, Application.csproj file, you’ll see /ItemGroup/PackageReference which points to WiseJ 2.5: <PackageReference Include=”Wisej-2″ Version=”2.5.*” />.

Same goes for VS2019 WiseJ templates (from troubleshooting page) – they also point to WiseJ 2.5.

I think you just need to take the templates that shipped with WiseJ 2.2 and got installed into /Documents/Visual Studio 2019/Templates and package it into a zip.

 

 

 

  • Levie (ITG)
    Hi Matthew, thanks for the update. We’ll get these fixed! Regards, Levie
  • You must to post comments
0
0

Gentlemen,

Any comments on my post from July 16?

  • You must to post comments
0
0

@Levie, @Frank.  I think I’ve gotten closer to resolving the problem.

I opened \Documents\Visual Studio 2022\Templates\ProjectTemplates\Visual C#\Wisej 2\WebApplication\Application.vstemplate and commented out the WizardExtension block and this template just magically worked.

  <!–
<WizardExtension>
<Assembly>
Wisej.Framework.Design.2022, Version=2.0.0.0, Culture=neutral, PublicKeyToken=17bef35e11b84171
</Assembly>
<FullClassName>Wisej.Design.Wizards.StartupProjectWizard</FullClassName>
</WizardExtension>
–>

Here is the problem.  I do not have an assembly on my system called Wisej.Framework.Design.2022.dll.  The closest I have is Wisej.Framework.Design.dll and via the Decompiler it does NOT have a class there called Wisej.Design.Wizards.StartupProjectWizard.

I have WiseJ 2.2.60 installed on my box.  I think, maybe the templates are making assumptions about various DLLs being present on the system that aren’t really there.

  • Levie (ITG)
    Hi Matthew, sorry didn’t see this. You can use your TP repo to get quicker support. It looks like there is an error in the VB WebApplication template. It should not have the Wizard. The Wizard is only for v2.5+. Installing 2.5 automatically registers Wisej.Framework.Design.2019 and Wisej.Framework.Design.2022. We’ll remove this wizard and re-upload them. Thanks for letting us know!
  • Matthew Ferry
    @Levie, the problem is present in all templates, not just VB WebApplication. When you do fix it and re-upload them, where exactly will the link be?
  • You must to post comments
0
0

Frank, I did run updateConfiguration command in an elevated Visual Studio prompt.

I ran procmon to see what is going on when you click Create.  Doesn’t seem like there is a NOT FOUND error anywhere.  So not sure whats going on.

 

  • You must to post comments
0
0

Hi Matthew,

not sure about that, but did you run the updateConfiguration command in an elevated Visual Studio prompt (i.e. as Administrator)?
Will probably have to dig deeper tomorrow.

Best regards
Frank

  • You must to post comments
0
0

Frank, I did get further.  I cleared the cache.  Ran the devenv /updateConfiguration command and I could now see the wisej templates in Visual Studio 2022.

However, when I pick any of the WiseJ templates and attempt to create a project, I get.  The system cannot find the file specified. (Exception from HRESULT: 0x80070002).
Any thoughts?

  • You must to post comments
0
0

Hi Matthew,

did you already check our documentation for that issue and followed the steps described here?

https://docs.wisej.com/docs/getting-started-1/troubleshooting

If it still fails, please let us know and we investigate further.

Best regards
Frank

  • You must to post comments
Showing 7 results
Your Answer

Please first to submit.