Visual-Studio
Visual-Studio copied to clipboard
1thenikita
VS 2022
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.
Support will be added soon.
If you need someone to test it, just let me know!
@1thenikita please add this extension in vs 2022 extension marketplace soon, we need it
@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 😊
@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!
@1thenikita It was already merged in https://github.com/1thenikita/Visual-Studio/pull/70, why was it reverted 😕 (https://github.com/1thenikita/Visual-Studio/pull/76)?
@1thenikita It was already merged in #70, why was it reverted 😕 (#76)?
Because Visual Studio 2019 and older did not work with the extension.
@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?
@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 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?
@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
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
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