#VS2017 – How to select the components to install in each WorkLoad (ie: avoid #Unity3D)


I’ve already written a couple of posts on the new installation experience in Visual Studio 2017 (link). I really like to have the chance to select workloads instead of selecting component one by one.


Note: In the latest Visual Studio 2017 RC version some of these workloads have disappeared since “have not passed the quality bar” for the final product. They will be published as packages apart to integrate with Visual Studio 2017.

An important detail when we use this method of installation is to make sure we only install what we need. For example, I am working with a Beta version of Unity3D and the default VS2017 installs an earlier version of Unity3D. At the end, I’ll have 2 versions of Unity3D, and this is something that I don’t need.

As well, let’s see how to do this in 2 simple steps.


  • We started with the Visual Studio 2017 Installation window.


  • When we select the Workload of “Game Development with Unity”, we can see how on the “Summary” section we can find the components that are installed.


  • If we uncheck Unity, we will see that we have… save 4 GB on disk space!


  • Another way to to this is to review the list of “Individual Components”.  We can find “Unity Editor ” in the “Games and Graphics” section.


  • And that’s it! We can begin installing our “custom” version of Visual Studio 2017 😀


Greetings @ Toronto

El Bruno


#VS2017 – nickname installation on Visual Studio!


I was installing the latest version of Visual Studio 2017 RC from scratch and I realize that now we have available the “nickname installation” option. This functionality had been presented some time ago, but it still wasn’t active for the general public.



Within the main view of installation, we can found this option in the bottom right as “Installation nickname”. The best way to explain this is think an scenario where you can have several instances of VS2017 side-by-side in the same computer.

This is especially useful when we have different configurations for different development environments.

Important: Visual Studio is not only a tool of .Net development. Now that it covers many different options, many platforms, languages, and more. That´s why this option to have these “installation sandboxes” as isolated environments is kind of interesting.

The operation is very simple. The first thing we must do is to define a nickname, for example, in this image I create an instance dedicated for development with HoloLens.


Once installed, you will see that we have a Visual Studio 2017 instance with the same name in our shortcuts or in the list of programs.


As well, until here is a novelty on the installation of the IDE. That Yes, I have to check how much shared space is common among facilities, because if you want invest + 30 GB of space for each instance, so unhelpful I see it on a laptop with a small disc.

Greetings @ Toronto

El Bruno

#VS2017 – Instalando con nicknames !



Mientras instalaba desde cero la última versión de Visual Studio 2017 RC, encontre disponible la opción de instalar con “nickname”. Esta funcionalidad, había sido presentada hace un tiempo, pero todavía no estaba activa para el público general.


Dentro de la vista principal de instalación, podemos ver en la zona inferior derecha la opción “Installation nickname”. La mejor forma de explicar esto, es pensar en que ahora con VS2017 podemos tener varias instalaciones side-by-side de Visual Studio en un mismo ordenador.

Esto es especialmente útil, cuando tenemos diferentes configuraciones para diferentes entornos de desarrollo.

Importante: Desde hace bastante tiempo, Visual Studio no es solo una herramienta de desarrollo .Net. Ahora que abarca muchas opciones diferentes, es interesante la opción de tener estos difernets sandboxes de instalación.

El funcionamiento es muy simple. Lo primero que debemos hacer es definir un nickname, por ejemplo, en esta imagen creao una instancia dedicada solo para el desarrollo con HoloLens.


Una vez instalada, veremos que tenemos una instancia de VS2017 con el mismo nombre en nuestros accesos directos o en la lista de programas


Pues bien, hasta aquí una novedad sobre la instalación del IDE. Eso sí, tengo que verificar cuanto espacio compartido es común entre instalaciones, porque si para cada instancia hay que invertira +30GB de espacio, pues poco util lo veo en un laptop con un disco pequeño.

Saludos @ Toronto

El Bruno