Error VS 2022

[peretodk]

426 2023/07/13 11:09:22.549 Error VisualStudio SetSite failed for package [EFCorePowerToolsPackage]Source: 'EFCorePowerTools' Description: Method not found: 'Microsoft.VisualStudio.Threading.JoinableTaskFactory Microsoft.VisualStudio.Shell.ThreadHelper.get_JoinableTaskFactory()'. System.MissingMethodException: Method not found: 'Microsoft.VisualStudio.Threading.JoinableTaskFactory Microsoft.VisualStudio.Shell.ThreadHelper.get_JoinableTaskFactory()'. at EFCorePowerTools.EFCorePowerToolsPackage.<InitializeAsync>d__11.MoveNext() at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine) at EFCorePowerTools.EFCorePowerToolsPackage.InitializeAsync(CancellationToken cancellationToken, IProgress`1 progress) at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass21_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e) at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck) {F4C4712C-CEAE-4803-8E52-0E2049D5DE9F}

---

0x80131513

[ErikEJ]

Please try the latest build .1535 - and which exact VS version do you have?

[jli-lhm]

Also not working for me and I have the latest .1535 build, clicking reverse engineer and nothing happens.

Microsoft Visual Studio Professional 2022 - Version 17.4.1

[ErikEJ]

@jli-lhm That sound like a different issue! But try to update to 17.6

[PeterMontgomery777]

I have the same problem on VS 17.5.5 with EF Tools which I think auto-updated itself to 2.5.1538 today.

[ErikEJ]

@PeterMontgomery777 I am unable to reproduce using VS 17.6, try to update to 17.6.5 (sorry for typo above)

[PeterMontgomery777]

Thanks for the quick response! I'll try updating VS later this afternoon and let you know.

[ErikEJ]

I am still trying to figure out what is going on here...

[PeterMontgomery777]

Thanks @ErikEJ, updating VS to 17.6.5 fixed it.

By the way, while you're here : I love the reverse engineering tool which I use quite often. The output has taught me a lot about DBContexts too. Thanks!

[ErikEJ]

@PeterMontgomery777 Glad you got it working!

If you like my free tools, I would be very grateful for a rating or review on Visual Studio Marketplace or even a one-time or monthly sponsorship

[peretodk]

Thanks Work with VS 17.6.5

[ErikEJ]

@AArnott @madskristensen

Version 17.5.4074 of Microsoft.VSSDK.BuildTools does not include the SDK files in the vsix!
Version 17.6.2164 of Microsoft.VSSDK.BuildTools does includes all the SDK files in the vsix!

This is what I have now - does it look sane?

    <PackageReference Include="Microsoft.VisualStudio.Data.Framework" Version="17.4.33103.184" />
    <PackageReference Include="Microsoft.VisualStudio.SDK" Version="17.0.32112.339" />
    <PackageReference Include="Microsoft.VSSDK.BuildTools">
      <Version>17.5.4074</Version>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
      <PrivateAssets>all</PrivateAssets>
    </PackageReference>

[ErikEJ]

I implemented a fix for this in the latest daily build, would be grateful if you could try it out.

[AArnott]

@ErikEJ Including copies of DLLs in your VSIX that VS itself ships can absolutely cause problems like this. The CLR may load your DLL instead of (or maybe in addition to, depending on load context) the ones in VS and screw up all kinds of things including things like this. It sounds like you removed them recently, which is great and should be the right way to go.

[ErikEJ]

@AArnott I did not "remove" them, I downgraded the build Tools version from 17.6 to 17.5 - I assume 17.6 caused them to be included.

[AArnott]

Well, however you did it, if your new VSIX doesn't include them, that's what counts. If 17.6 VS SDK buildtools 'added' them, that sounds like a serious bug that ... might even be known about internally already. I heard rumors.

[ErikEJ]

@@AArnott Thanks a lot. If you need help with the 17.6 issue let me know.

[Gargaj]

I implemented a fix for this in the latest daily build, would be grateful if you could try it out.

Just for the sake of whoever is googling the same error for a different project and is looking for a fix, the fix was 2b627a9 :)

[BlackbirdSQL]

It seems this thing has reared it's ugly head again in Visual.Studio.SDK 17.9.37000.

[ErikEJ]

@BlackbirdSQL yes, I reported this here: VsixCommunity/Community.VisualStudio.Toolkit#432