Question: State of C++/CLI with dotnet

[cdecompilador]

As I currently understand even though dotnet cli works very well with CLR family languages, when it comes to C++ its tightly bound to Visual Studio still, mainly because .vcxproj doesn't have all the default built-in behaviour, props and targets that .csproj and .fsproj have.

My question is about the current planning of C++ (and C, MASM by extension) on the open source space, and if it will be included as a main part of the SDK in the future and not as an optional extension that only works with Visual Studio.

[marcpopMSFT]

I'm not aware of any planned investments in improving the dotnet CLI experience for c++ or C++/cli projects. Including
@olgaark @lukka to comment.

[olgaark]

Marc is correct - currently, there are no plans for any changes in this area.
The primary focus of C++ support is native code (so it would be illogical to have it as a part of .NET SDK) and MSVC compiler and libraries currently can only be installed as a part of VS.

[cdecompilador]

thanks for your time