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."
-
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.
-
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.
but they did. natemcmaster commented 12 minutes ago It appears Visual Studio bundled the wrong build of the CLI. @livarcocc's team is working with the VS team to investigate fixes. I'm going to close this as a duplicate of dotnet/cli#9897. The recommended workaround is to uninstall 2.1.401, download the correct 2.1.401 installers from https://www.microsoft.com/net/download/dotnet-core/2.1, and install those instead. This appears to fix it, but you may have to do a
dotnet restore -f
at the root dir of the solution.
"Time flies like an arrow. Fruit flies like a banana."
-
but they did. natemcmaster commented 12 minutes ago It appears Visual Studio bundled the wrong build of the CLI. @livarcocc's team is working with the VS team to investigate fixes. I'm going to close this as a duplicate of dotnet/cli#9897. The recommended workaround is to uninstall 2.1.401, download the correct 2.1.401 installers from https://www.microsoft.com/net/download/dotnet-core/2.1, and install those instead. This appears to fix it, but you may have to do a
dotnet restore -f
at the root dir of the solution.
"Time flies like an arrow. Fruit flies like a banana."
Matthew Dennis wrote:
but they did.
Nope... A MS worker did it. It is nto the same ;) :laugh:
Matthew Dennis wrote:
This appears to fix it, but you may have to do a
dotnet restore -f
at the root dir of the solution.
But that only if you have previously installed the buggy version, or always?
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."
-
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."
Ah, the advantage of not having any .NET SDK installed at all.
-
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 had a bug with 15.8.1 and they rushed out a fix that repaired the problem there. With that one, the resource file plug-in wouldn't load so I couldn't edit resource files.
In 15.8.1 they also broke support for the Italian keyboard layout (fixed in 15.8.2): you couldn't type closing curly braces for the entire month of August :-D I guess it's a good thing it happened in the month during which most of Italy is on vacation! :laugh:
Luca The Price of Freedom is Eternal Vigilance. -- Wing Commander IV En Það Besta Sem Guð Hefur Skapað, Er Nýr Dagur. (But the best thing God has created, is a New Day.) -- Sigur Ròs - Viðrar vel til loftárása
-
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."
-
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.