Don't update Visual Studio to 15.8.2
-
Something went wrong and the new SDK 2.1.401 references a version of the Microsoft.NETCore.App that is on a MyGet feed and should not be in a release. This results in programs that compiled before the upgrade to fail. You can 'fix' this with a global.json file which pins the SDK to 2.1.400 (the previous SDK version) or by uninstalling the new SDK. I've made MS aware of the issue, and they are scrambling to rectify the problem, which should not have happened and they admit they screwed up somewhere in the release process. The Issue on GitHub invalid Microsoft.NETCore.App after upgrade to SDK 2.1.401 · Issue #3474 · aspnet/Home · GitHub[^]
"Time flies like an arrow. Fruit flies like a banana."
-
Matthew Dennis wrote:
happened and they admit they screwed up somewhere in the release process.
I would not bet they do it publicly ;)
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Something went wrong and the new SDK 2.1.401 references a version of the Microsoft.NETCore.App that is on a MyGet feed and should not be in a release. This results in programs that compiled before the upgrade to fail. You can 'fix' this with a global.json file which pins the SDK to 2.1.400 (the previous SDK version) or by uninstalling the new SDK. I've made MS aware of the issue, and they are scrambling to rectify the problem, which should not have happened and they admit they screwed up somewhere in the release process. The Issue on GitHub invalid Microsoft.NETCore.App after upgrade to SDK 2.1.401 · Issue #3474 · aspnet/Home · GitHub[^]
"Time flies like an arrow. Fruit flies like a banana."
I'm not using Core yet, so no problem?
My apologies for the previous sig block. It's been ages since I posted anything on here.
-
Nelek wrote:
I would not bet they do it publicly
Do you announce your bugs publicly? :-D
Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
That's exactly why I said that... strange enough... the dev did it.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
I'm not using Core yet, so no problem?
My apologies for the previous sig block. It's been ages since I posted anything on here.
-
Something went wrong and the new SDK 2.1.401 references a version of the Microsoft.NETCore.App that is on a MyGet feed and should not be in a release. This results in programs that compiled before the upgrade to fail. You can 'fix' this with a global.json file which pins the SDK to 2.1.400 (the previous SDK version) or by uninstalling the new SDK. I've made MS aware of the issue, and they are scrambling to rectify the problem, which should not have happened and they admit they screwed up somewhere in the release process. The Issue on GitHub invalid Microsoft.NETCore.App after upgrade to SDK 2.1.401 · Issue #3474 · aspnet/Home · GitHub[^]
"Time flies like an arrow. Fruit flies like a banana."
-
Something went wrong and the new SDK 2.1.401 references a version of the Microsoft.NETCore.App that is on a MyGet feed and should not be in a release. This results in programs that compiled before the upgrade to fail. You can 'fix' this with a global.json file which pins the SDK to 2.1.400 (the previous SDK version) or by uninstalling the new SDK. I've made MS aware of the issue, and they are scrambling to rectify the problem, which should not have happened and they admit they screwed up somewhere in the release process. The Issue on GitHub invalid Microsoft.NETCore.App after upgrade to SDK 2.1.401 · Issue #3474 · aspnet/Home · GitHub[^]
"Time flies like an arrow. Fruit flies like a banana."
Thanks for the warning. One recent update killed my Intel compiler so it wouldn't run. I ended up uninstalling it. So much for updates. I guess they fired their QA department and we're the testers instead. Nice going!
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." -- Marcus Brigstocke, British Comedian
-
Thanks for the warning. One recent update killed my Intel compiler so it wouldn't run. I ended up uninstalling it. So much for updates. I guess they fired their QA department and we're the testers instead. Nice going!
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." -- Marcus Brigstocke, British Comedian
-
The Intel Fortran compiler failing with vs 15.8 is Intel's fault (they have admitted it). They did not update their Visual Studio integration for 15.8; it only works for 15.7. They say they are going to fix it "later this year".
-
Thanks. I was wondering.
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." -- Marcus Brigstocke, British Comedian
-
Ah, the advantage of not having any .NET SDK installed at all.