Writing Visual Studio Extensions with Mads - 64bit extensions for Visual Studio 2022

Visual Studio 2022 is going to be 64-bit. In this episode we're looking at how to write extensions for 64-bit Visual Studio 2022

#vsix #vs2022

[frankhaugen]

I'd like to see the next version have support for scripts to do work on the code, (I find myself always having a console app ready to run refactoring or something because even the replace text is too slow or simply crashes). And extensions should be in the form of Nugets and runtime installable.

[fullduckdev]

36:34 Those are called preprocessor variables as they're defined before the build and cannot change without re-compiling

[ThePatify]

12:00 "If you've done an extension in .NET, and you are compiling in AnyCPU which is the default, then you're good, you don't have any issue like going to 64 bits" yippee thanks Mads :)

[anna-jaynemetcalfe]

I'm a bit late to the party (I just started looking at our extensions today), but it occurs to me that info on how to port native C++ plugins to VS2022 is very thin on the ground. Any tips or pointers (e.g. at more native extensibility orientated content or channels) would be useful.

[TaoriUTS]

It's ironic how such a large company picks up on idea's so quickly and evolves continuously, while <500 companies act like they want to be microsoft, by blindly copying things other companies even if they make no sense whatsoever. MS sure seems innovation and self reflection driven (especially if you consider the huge company size)