L
Levon Grice
Guest
So let me get this straight and please correct me if I'm wrong. If I want to develop a web application with the latest and greatest releases of the .NET core SDK, I can use VS 2019, because it supports .NET Core SDK 2.2.300 and higher. However, if I want to deploy it to Azure web apps, I have to go back to VS 2017 and use .NET Core SDK 2.2.107 or lower.
Does this sound about right? Seems the upgrade to VS 2019 has tied my hands in more ways than one. Yes yes I know I can have both installed side by side, blah blah blah. It's just annoying to have to use two IDE's from the same company due to compatibility issues from one release to the next.
Hey everyone! Here is our latest IDE with all these bells and whistles! Use it! It's awesome! But here are a few things you can't do with our latest and greatest tool that you'll have to go back to VS 2017 for. Sorry folks.
Am I missing something here?
Continue reading...
Does this sound about right? Seems the upgrade to VS 2019 has tied my hands in more ways than one. Yes yes I know I can have both installed side by side, blah blah blah. It's just annoying to have to use two IDE's from the same company due to compatibility issues from one release to the next.
Hey everyone! Here is our latest IDE with all these bells and whistles! Use it! It's awesome! But here are a few things you can't do with our latest and greatest tool that you'll have to go back to VS 2017 for. Sorry folks.
Am I missing something here?
Continue reading...