VS 2022

[monke8555]

Is your feature request related to a problem? Please describe:

I got VS 2022, so this extension doesn't work in it. I know it's in preview, but afaik it shouldn't be hard to add support for it.

Solution:

Add VS 2022 support.

[tyllastarr]

I would like to second this idea.

[1thenikita]

Support will be added soon.

[tyllastarr]

Support will be added soon.

If you need someone to test it, just let me know!

[Kaffu093]

I'm impatient for this one.

[0xRapidFire]

Still awaiting for the support.. @1thenikita

[hootanht]

@1thenikita please add this extension in vs 2022 extension marketplace soon, we need it

[1thenikita]

@1thenikita please add this extension in vs 2022 extension marketplace soon, we need it

Hi. I have begun work on preparing an extension for version 2022. We will try to fix it soon and post the update 😊

[Kaffu093]

@1thenikita please add this extension in vs 2022 extension marketplace soon, we need it

Hi. I have begun work on preparing an extension for version 2022. We will try to fix it soon and post the update 😊

Nice, thank you!

[ghost]

When? :)

[PsychoPast]

Any update?

[hootanht]

@tyllastarr waiting ...
please vote for this comment

[rollingmoai]

@1thenikita It was already merged in #70, why was it reverted 😕 (#76)?

[1thenikita]

@1thenikita It was already merged in #70, why was it reverted 😕 (#76)?

Because Visual Studio 2019 and older did not work with the extension.

[ghost]

@1thenikita It was already merged in #70, why was it reverted 😕 (#76)?

Because Visual Studio 2019 and older did not work with the extension.

Why not create two builds as a workaround?

[rollingmoai]

@1thenikita It was already merged in #70, why was it reverted 😕 (#76)?

Because Visual Studio 2019 and older did not work with the extension.

Why not create two builds as a workaround?

Example: VSColorOutput, VSColorOutput64

[1thenikita]

@1thenikita It was already merged in #70, why was it reverted 😕 (#76)?

Because Visual Studio 2019 and older did not work with the extension.

Why not create two builds as a workaround?

Two builds, if I'm not mistaken, cannot be locked into the Visual Studio Marketplace.
And going out, as below, for two extensions, I think is not the best option: you would have to duplicate the code several times, look at different suggestions, why when you can combine in 1 repository?

[ghost]

@1thenikita It was already merged in #70, why was it reverted 😕 (#76)?

Because Visual Studio 2019 and older did not work with the extension.

Why not create two builds as a workaround?

Two builds, if I'm not mistaken, cannot be locked into the Visual Studio Marketplace. And going out, as below, for two extensions, I think is not the best option: you would have to duplicate the code several times, look at different suggestions, why when you can combine in 1 repository?

Create two marketplace pages for the same repository.

Example:

https://marketplace.visualstudio.com/items?itemName=josefpihrt.Roslynator2019
https://marketplace.visualstudio.com/items?itemName=josefpihrt.Roslynator2022

[ghost]

I created a (temporary) fork with the changes applied for VS 2022: https://github.com/Majestro000/Visual-Studio
Build with VS 2022 and install by bin\Debug\DiscordRPforVS.vsix

[rollingmoai]

I created a (temporary) fork with the changes applied for VS 2022: https://github.com/Majestro000/Visual-Studio Build with VS 2022 and install by bin\Debug\DiscordRPforVS.vsix

There is already this fork: https://github.com/CursedSheep/DiscordRPC-Visual-Studio-2022