After moving the extension code to Shared Project all my XAML files seemed to be broken and XAML Visual Designer couldn’t load them correctly to display preview.
I tried this approach and lost 4 hours of my life. Each VSIX project has its own vsixmanifest file and references appropriate nuget packages. So what can we do about that? According to the migration guideline on MSDN, the recommended approach is to move all extension code to Shared Project and reference it from two separate VSIX projects - one for VS2019 (and older) and one for VS2022 (and newer). However, those changes are not backward compatible and our extension can’t be installed on an older version of VisualStudio anymore (adjusting InstallationTarget.Version won’t help).
Ok, that’s all - it doesn’t seem to be a lot of work as I said before. Runtime build native contentfiles analyzers buildtransitiveĪdditionally, you need to change the dotnet framework version to v4.7.2, if you still have an older version: The next thing that needs to be done is upgrading SDK NuGet package to a version appropriate for VS2022: Ĭompile build native contentfiles analyzers buildtransitive First of all, you need to adjust vsixmanifest by adding the new attribute ProductArchitecture to InstallationTarget configuration: What needs to be changed 🔗︎īasically, two things need to be changed to migrate your extension to VS2022. I wanted to postpone the migration a little bit more but I got an email from one of my paid customers, that the need for constant switching between VS2022 and V2019 to use my MappingGenerator extension is killing his productivity - and I couldn’t allow for that to happen. After quick scanning of migration guideline it turned out that changing InstallationTarget was not enough and more work was required to support VS2022. Recently, the Visual Studio 2022 Preview was published. The migration was straightforward: it required only to extend InstallationTarget range to [15.0,17.0) in vsixmanifest, re-compile, and of course, re-publish the extension to the Visual Studio marketplace. It was initially created for Visual Studio 2017, but a few months later Visual Studio 2019 came out and I needed to support it as I was one of the beneficent. The new changes in Visual Studio 2022 17.2 are quite technical and long-winded to explain but you can check out the fairly comprehensive explanations in Microsoft’s announcement on its Dev Blog.I published my first VisualStudio extension on 26th February 2018. These seem like some pretty annoying issues to have had to contend with so, hopefully, the 17.2 update makes things a lot better. Some of the most upvoted issues that were fixed in this update include ‘Window switching in Windows 11 taskbar stops working when application is debugging in VS 2022’, ‘An error occurred while initializing the frame’s content’, and ‘visual studio 2022 hangs randomly’. On top of all the new features VS 2022 17.2 delivers, Microsoft has addressed more than 400 issues given as feedback by the community. In addition to this release, Microsoft has made Visual Studio 2022 17.3 Preview 1 available for download which brings tooling support for. NET experiences, Git performance, there are updates for C++, and new Azure tools for local development and deployment. Microsoft has released Visual Studio 2022 17.2, it improves C# and.
0 kommentar(er)
