Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Don't update Visual Studio to 15.8.2

Don't update Visual Studio to 15.8.2

Scheduled Pinned Locked Moved The Lounge
helpannouncementcsharpasp-netvisual-studio
20 Posts 14 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Nelek

    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.

    Z Offline
    Z Offline
    ZurdoDev
    wrote on last edited by
    #11

    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.

    N 1 Reply Last reply
    0
    • M Matthew Dennis

      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."

      R Offline
      R Offline
      Richard Jones
      wrote on last edited by
      #12

      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.

      R 1 Reply Last reply
      0
      • Z ZurdoDev

        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.

        N Offline
        N Offline
        Nelek
        wrote on last edited by
        #13

        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.

        1 Reply Last reply
        0
        • R Richard Jones

          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.

          R Offline
          R Offline
          Rick York
          wrote on last edited by
          #14

          I don't use it either and there have been no problems for me.

          1 Reply Last reply
          0
          • M Matthew Dennis

            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."

            O Offline
            O Offline
            obermd
            wrote on last edited by
            #15

            I was thinking you were alerting us to the crappy UI. VS 15.8.2 freezes a lot and the so-called "Blue (High Contrast)" scheme should be called "Blue (No Contrast)".

            1 Reply Last reply
            0
            • M Matthew Dennis

              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."

              E Offline
              E Offline
              Erik Burd
              wrote on last edited by
              #16

              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

              O 1 Reply Last reply
              0
              • E Erik Burd

                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

                O Offline
                O Offline
                ols6000
                wrote on last edited by
                #17

                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".

                E 1 Reply Last reply
                0
                • O ols6000

                  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".

                  E Offline
                  E Offline
                  Erik Burd
                  wrote on last edited by
                  #18

                  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

                  O 1 Reply Last reply
                  0
                  • E Erik Burd

                    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

                    O Offline
                    O Offline
                    ols6000
                    wrote on last edited by
                    #19

                    In case you were wondering how to get Intel Fortran to work under VS2017, you have to uninstall VS 15.8.2 (or .1) and then install VS 15.7.x.

                    1 Reply Last reply
                    0
                    • J Joe Woodbury

                      Ah, the advantage of not having any .NET SDK installed at all.

                      A Offline
                      A Offline
                      Abbas A Ali
                      wrote on last edited by
                      #20

                      You must be a believer of No Code[^]. :laugh:

                      1 Reply Last reply
                      0
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • World
                      • Users
                      • Groups