[#VS2013] Solution Start Page, mark this one to be used in events

Hi!

As I mentioned yesterday, the Microsoft DotNet Spain Conference is very near, and as always, in these sessions with more or less 60 minutes, is very convenient to have all the code examples at hand. An usual option is to have the shortcuts into a single site and load them from there, but to keep learning, always have to try new things. And today I find this extension “Solution Start Page“.

Once installed, we can activate the customizable Start Page, directly from the Visual Studio options

Clipboard01

And then the Start Page has 2 modes. Edit mode, where you can edit different sections with shortcuts to local solutions

Clipboard02

And then the option to use Classic where we will see the same

Clipboard04

The truth that very interesting, I will give you a couple of months of testing and see what 😀

Greetings @ Home

/El Bruno

Download: https://visualstudiogallery.msdn.microsoft.com/de5a8b10-d521-43ba-8af4-938c19b10ec9

[#VS2013] Global Zoom Level, a great one

Hello!

Today a short post about an extension that is simple and useful:

Change the level of zoom in an editor and this extension saves the values by default to be replicated in the other IDE windows in Visual Studio

When doing some Pair Programming or working with Visual Studio in a presentation and you change the zoom level, it is likely to want to keep this change on all editors that you have open. Since the IDE is so special, it does not. Just keep it in the window where you have applied it… now you can see the interesting thing that this extension!

A video that a couple of words as always best

Change Zoom

Download: https://visualstudiogallery.msdn.microsoft.com/59260ee8-5e2d-4ca7-8dc5-4efcf7b61a81

Saludos @ Madrid

/El Bruno

[#VS2013] Global Zoom Level, simplemente genial

Hola!

Hoy toca un post cortito, sobre una extensión que hace algo simple y muy útil:

Cambias el nivel de zoom en un editor y la extensión lo guarda por defecto para ser replicado en las demás ventanas del IDE de Visual Studio

Cuando estas haciendo un poco de Pair Programming o trabajando con Visual Studio en una presentación y cambias el nivel de zoom, lo más probable es que quieras que este cambio se mantenga en todos los editores que tengas abierto. Pues el IDE es así de especial, no lo hace. Solo lo mantiene en la ventana donde lo has aplicado … ahora ves lo interesante que esta extensión !!!

Como siempre mejor un video que un par de palabras

Change Zoom

Descarga: https://visualstudiogallery.msdn.microsoft.com/59260ee8-5e2d-4ca7-8dc5-4efcf7b61a81

Saludos @ Madrid

/El Bruno

[#NETMF] NET MicroFramework updated to version 4.3 RTM and templates availables for Visual Studio 2015

Hello!

While I’m airport at airport, try to finish tuning the demos for 2 sessions that I will have in the Microsoft dotNet Spain Conference. After giving me head on the wall a while, 2 weeks ago with NetDuino and Visual Studio 2013, I see that .net MicroFramework friends have updated installers for Visual Studio, 2012, 2013, and 2015; and we also have a new version of NETMF > SDK v4.3 (QFE2-RTM)

You can download the SDK and templates from

  • NET Micro Framework SDK 4.3 (QFE2)

https://visualstudiogallery.msdn.microsoft.com/4dd0fc66-a0dc-4d9f-8cb4-5a8782c90eee

  • . NET Micro Framework VS2015 Project System

https://visualstudiogallery.msdn.microsoft.com/d90dcb48-d566-4bab-8ef1-0c7927758f9e

  • . NET Micro Framework VS2013 Project System

https://visualstudiogallery.msdn.microsoft.com/71212f3c-4188-4c55-9407-72cb06907e52

  • . NET Micro Framework VS2012 Project System

https://visualstudiogallery.msdn.microsoft.com/53a788d7-286b-414b-a780-773abf78bc27

Greetings @ Madrid

/El Bruno

[#NETMF] Net MicroFramework actualizado a 4.3 RTM y ya tenemos templates para Visual Studio 2015

Hola!

Mientras ando de aeropuerto en aeropuerto, intento terminar de afinar las demos para las 2 sesiones que tendré en la Microsoft dotNet Spain Conference. Después de darme con la cabeza en la pared un buen rato, hace 2 semanas con NetDuino y Visual Studio 2013, veo que los amigos de .Net MicroFramework han actualizado los instaladores para Visual Studio 2012, 2013 y 2015; y que además tenemos una nueva versión de NETMF > SDK v4.3 (QFE2-RTM)

El SDK y las plantillas se pueden descargar desde

Saludos @ Madrid

/El Bruno

[#GALILEO] Hello World with #VisualStudio 2013

Hello!

Let’s move on with the Intel Galileo series of posts:

In today’s post I’ll create a basic “hello world” for Intel Galileo. As usual with this boards, this sample is try to make the LED in pin 13 to Blink 😉

So, we open Visual Studio 2013 and create a new project “Visual C++ \\ Windows for IoT \\ Galileo Wiring App

ga01

Once the project is created, it already has inside all the stuff to make the led bonk. However, before we try to deploy this app, a nice check is good to validate if everything is fine.

In example, if you change the name of the board when you create the bootable SD, some changes are required. Galileo Watcher app will display the devices on the network, in the following sample the device name is ebgal01

ga02

Visual Studio will try to connect and deploy the compiled app, so a couple of configurations are required. In the projcet properties, the value for Remote Server Name, must be replaces with the name of the device (you can also put here the device IP Address). You can also check the [Working Directory] property, it defines the location where VS will deploy / copy the compiled app.

ga03

Now let’s move to security. By default Windows authentication is defined. Unless you create a bootable SD with no authentication, do not change this one.

ga04

When you start the deploy, VS will ask for user and password.

ga05

And once you put all correct values, you can access the remote file system of the device, and you will see the deplooyed app in the directory [C.\Temp\] .

ga06

Saludos @ Home

/El Bruno

[#GALILEO] Hola mundo desde #VisualStudio 2013

Hola !

Sigo con la serie de posts sobre Intel Galileo

En el post de hoy, mostraré como hacer un “hello world” en Intel Galileo. Que no es ni más ni menos, que hacer parpadear un LED en el pin 13.

Lo primero es abrir Visual Studio 2013 y crear un nuevo proyecto de tipo “Visual C++ \\ Windows for IoT \\ Galileo Wiring App

ga01

El proyecto que se crea por defecto ya posee todo lo necesario para implementar un Blinking Led. Sin embargo, es conveniente revisar un par de cosas antes de compilar y hacer un deploy.

Por ejemplo, si has cambiado el nombre con el que se inicia tu Galileo (desde la tarjeta SD creada en este post), tendrás que hacer algunos cambios. La app Galileo Watcher muesta los devices conectados a la red, en este caso el nombre del device es ebgal01

ga02

Para que Visual Studio pueda reconocer el dispositivo y desplegar la app en el mismo hay que modificar algunas propiedades del proyecto. La propiedad Remote Server Name, debe tener el nombre del device. (otra opción es poner la dirección IP del device en lugar del nombre). Otra propiedad interesante es [Working Directory] que define la ubicación en donde Visual Studio desplegará la app.

ga03

Otro punto a tener en cuenta es la seguridad con la que Visual Studio se conectará para desplegar la app. El valor por defecto es que se utilicen credenciales Windows. Salvo que hayas creado una SD booteable sin seguridad esta opción es la que debes utilizar.

ga04

Para comprobar esto, cuando lanzas un deploy Visual Studio te pedirá usuario y contraseña.

ga05

Una vez que has introducido todos los datos correctamente, la app se despliega en el Intel Galileo. Si accedes al sistema de archivos puedes ver que en el directorio [C.\Temp\] está un executable con la app creada.

ga06

Saludos @ Home

/El Bruno

[#GITHUB] With GitHub Student Developer Pack, now you have … #VisualStudio: D #OhYeah

0508.vsgh.jpg-550x0

Hello!

I just finish a post where I really appreciate the move of some Microsoft contents to GitHub, and then I found with this killer news from GitHub, specially for students

With your Github Student Developer Pack subscription, you also have access to a license of Visual Studio and all the advantages of the DreamSpark program.

And you also have other benefits such as tools, resource stack in the cloud, etc. Everything needed so that a student can take forward an idea 😀

Greetings @ Home

/El Bruno

Source:

https://education.github.com/pack

https://www.dreamspark.com/

http://blogs.msdn.com/b/uk_faculty_connection/archive/2015/01/12/visual-studio-team-moves-source-to-github-and-offers-visual-studio-as-part-of-the-github-student-developer-pack.aspx

PS: If you haven’t, take a look at DreamSpark. It is a very important resource that provides Microsoft giving access to software for learning, teaching and research purposes.

[#GITHUB] Con el GitHub Student Developer Pack, ahora tienes … #VisualStudio :D #OhYeah

0508.vsgh.jpg-550x0

Hola!

Pues eso, que no bien termino de escribir un post dando gracias a los amigos de Microsoft por mover contenidos a GitHub, que ya van los de GitHub, y se sacan esto de la manga

Con tu suscripcion de Github Student Developer Pack, también tienes acceso a una licencia de Visual Studio y a todas las ventajas del programa DreamSpark.

Y además, tienes otra pila de beneficios como herramientas, recursos en el cloud, etc. Todo lo necesario para que un estudiante pueda sacar adelante una idea 😀

Saludos @ Home

/El Bruno

Fuente:

https://education.github.com/pack

https://www.dreamspark.com/

http://blogs.msdn.com/b/uk_faculty_connection/archive/2015/01/12/visual-studio-team-moves-source-to-github-and-offers-visual-studio-as-part-of-the-github-student-developer-pack.aspx

PD: Si no lo conoces, dale un vistazo a DreamSpark. Es un recurso muy importante que proporciona Microsoft dando acceso a software para fines de aprendizaje, enseñanza e investigación.

[#VS2015] HowTo: Show more detail in a local build in the Visual Studio IDE

Hello!

Many times I face myselft with Visual Studio solutions that take a long time in the basic step of bulld and run unit tests. When I attempt to help or ask for help to see something with “bad smell” I’m amazed with the following

Many people are not aware that by default, the level of logging in a Build in Visual Studio IDE is Minimal!

I learned this one many years ago when I was fighting with the Team Foundation Server 2005 builds. The following are possible values for the Build log detail:

  • Minmal (default)
  • Normal
  • Detailed
  • Diagnostic

Surely they are familiar if you’ve worked with trace or logging. And see the difference between a build in Minimal mode

b01

And one in Normal mode

b03

We have times, executed lines, commands and variables of compilation, etc.

Set the verbosity level is within the options in the IDE, in the section “Project and Solutions / / Build and Run

b04

Another important detail is that we can change the level of detail both to the Visual Studio Output and as for the build log. Personally I recommend

Have the project build from IDE to Normal and build Detailed log file

This is usually more than enough. And before that you forget me, this applies to believe that all versions of Visual Studio.

Greetings @ Home

/El Bruno