In #967 @kieferrm writes:
Right. But since when isn't VSCodium a "Visual Studio family product"? It's quite clear that it is, given that it's built off the VS Code source code. The differences are minimal and not relevant in this context. It's clearly a "Visual Studio family product".
So, can you please remove the restriction in this extension such that VSCodium can use it fully? There's no point in not letting users of VSCodium use it the same way that they would if they were running VS Code.
Again, the differences between these two builds of the VS Code source code are minimal and of a completely different nature than what is relevant to this extension - the two builds would use and communicate with the extension in the very same way, hence the differences in the builds aren't practically relevant to this extension at all.
In #967 @kieferrm writes:
Right. But since when isn't VSCodium a "Visual Studio family product"? It's quite clear that it is, given that it's built off the VS Code source code. The differences are minimal and not relevant in this context. It's clearly a "Visual Studio family product".
So, can you please remove the restriction in this extension such that VSCodium can use it fully? There's no point in not letting users of VSCodium use it the same way that they would if they were running VS Code.
Again, the differences between these two builds of the VS Code source code are minimal and of a completely different nature than what is relevant to this extension - the two builds would use and communicate with the extension in the very same way, hence the differences in the builds aren't practically relevant to this extension at all.