4 ms·

As someone who uses visual studio + code literally every day, I'm not sure what you're referring to with most of these complaints. The project/solution files a

by eyegor 7y ago

As someone who uses visual studio + code literally every day, I'm not sure what you're referring to with most of these complaints. The project/solution files are bog standard xml, and well documented, but in general you shouldn't need to touch them. The migration from framework to core 3.0 is now very simple thanks to xaml support, but it used to be a huge hassle. You can literally just edit the tags in your csproj/fsproj/etc to enable different target frameworks, or you can use the ui [0], and then you'll need to do a nuget reinstall. One command [1]. As for running into bugs, they built bug/feature requests into the visual studio 2019 ide, or you can access it via the website [2]. They are usually very responsive, typically something within a couple of days. [0] https://stackoverflow.com/questions/57334018/visual-studio-2019-select-framework-version-for-net-core-class-library-projec https://stackoverflow.com/questions/57334018/visual-studio-2... [1] open package manager console, type 'update-package -reinstall'. [2] https://developercommunity.visualstudio.com https://developercommunity.visualstudio.com

Nullabillity 7y ago
> The project/solution files are bog standard xml, and well documented, but in general you shouldn't need to touch them. Project files are "bog standard" XML (except for all the weird magic, like variable resolution and conditionals), but solution files are some unholy VB-like abomination. But regardless, that doesn't help much when the schema is clearly not designed for human editing (incredibly verbose, UUIDs everywhere for references, etc). > The migration from framework to core 3.0 is now very simple thanks to xaml support, but it used to be a huge hassle. No idea how a GUI description language is supposed to help you here. > You can literally just edit the tags in your csproj/fsproj/etc to enable different target frameworks Didn't work for me. > or you can use the ui [0], and then you'll need to do a nuget reinstall. One command [1]. Keep in mind that that command is free to update dependencies as it feels like.

by eyegor 7y ago

Nullabillity 7y ago

> The project/solution files are bog standard xml, and well documented, but in general you shouldn't need to touch them. Project files are "bog standard" XML (except for all the weird magic, like variable resolution and conditionals), but solution files are some unholy VB-like abomination. But regardless, that doesn't help much when the schema is clearly not designed for human editing (incredibly verbose, UUIDs everywhere for references, etc). > The migration from framework to core 3.0 is now very simple thanks to xaml support, but it used to be a huge hassle. No idea how a GUI description language is supposed to help you here. > You can literally just edit the tags in your csproj/fsproj/etc to enable different target frameworks Didn't work for me. > or you can use the ui [0], and then you'll need to do a nuget reinstall. One command [1]. Keep in mind that that command is free to update dependencies as it feels like.