none
Visual Studio 2015 why on earth this VS2015 installation screwes the entire computer set up?

    Question

  • I am not sure if Microsoft is noticing that it is falling apart due to poor release management of Visual Studio.

    VS 2015, It been a hell as I have been facing with this version many different ways.

    I recently installed one component, Office Products, which screwed other unrelated component, apache cordova.

    I had to again uninstall entire VS and reinstall, now it removed all my task bar icons.

    What the hell happening around, I could not understand!!!

    Microsoft must serious think about good release manager there, Microsoft will have Directors as their heads, there are mostly nontechies and 1/2 baked fellow speaking fancy around heading the departments but there seems to be situation has been resulting to more and more worsen w.r.t VS tools and releases.

    They are wasting hell lot of developer and client's time with release those are "incomplete" and "later releasing the KB" to fix the earlier bugs with incomplete releases.

    Microsoft better bring in some techies here as directors instead of mgmt geeks.


    Ekambar Rao

    Saturday, March 25, 2017 11:31 AM

All replies

  • Hi Ekambar,

    FWIW, Microsoft knows that the setups Visual Studio 2002-2015 and subsequent service packs or updates can cause problems because of poor isolation. They are fixing it in VS 2017 with these approaches:

    1) The VS 2017 setup is incredibly modular. You install just the "workloads" / "individual components" that you need.

    2) VS 2017 uses its own private Registry key, which isolates VS 2017 from other VS versions, and cannot screw the whole computer.

    3) VS 2017 avoids the Global Assembly Cache (GAC) to install files, using its own private folders.

    As a result of 2 and 3, several VS 2017 editions (Community, Professional, Enterprise) can coexist on the same machine, something never seen before.

    4) They can ship frequent updates to fix things that unfortunately may ship broken. As example, an update was released just a few days after the RTM.

     


    My portal and blog about VSX: http://www.visualstudioextensibility.com; Twitter: <a href="https://twitter.com/VSExtensibility">https://twitter.com/VSExtensibility</a> MZ-Tools productivity extension for Visual Studio: <a href="https://www.mztools.com">https://www.mztools.com</a>

    Sunday, March 26, 2017 4:47 PM
  • Hi, 

    Visual studio 2017 has been improved.

    --remove <workload or component ID> [<workload or component ID> ...] Optional: One or more workload or component IDs to remove. For more information, see our Workload and component IDs page.

    After you install visual studio 2017, you could use the command to uninstall some components. Besides, there are more command line for customizing the installation.

    Refer: https://docs.microsoft.com/en-us/visualstudio/install/use-command-line-parameters-to-install-visual-studio

    Best regards,

    Joyce


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, April 4, 2017 7:47 AM
  • Tomorrow is always brighter than today and yesterday.....

    This is what I can understand from Microsoft releases..... :-)

    But the problems in some or other way persists and continues.


    Ekambar Rao

    Thursday, May 4, 2017 4:32 AM