[# VS11] Some points to keep in mind when working with the new Team Build for Team Foundation Service

image

Buenas,

a few days ago Brian Harry made public the news where commented that we can already count with a Team Build Server in our service of Team Foundation Service. Put another way, this means that we have at our disposal a Team Build Server in TFS on the cloud. Just great! (Friend Vincenc has also written a post about it)

This has many great advantages, but we also have to take into account several things to work with this model.

image

Important: We do not have access to the physical machine from Team Build

This means that we cannot change anything in it so that our projects compile, run unit tests, etc. in this server. I personally think that this is great, a software project should be able to be compiled and packaged only from the contents in the Source Control repository.

If you use COM components, or work with an environment of compilation that requires you to install something in it to be able to compile, because you’ll have to revise your model of development to use Team Build in Team Foundation Service.

Initially the Team Build single VM will be installed

-Visual Studio 2010 SP1

- Visual Studio 11 Beta

Java for now nothing at all… Although clear, it will be in the final package, as ECLIPSE with Maven 2 and Maven 3 customers need.

I have done the test of the "Hello World" for Team Build in 10 minutes and works great, although if instead of MSTests use XUnit or NUnit, because you have to devote a few minutes to Setup.

Finally, an interesting detail. When we define the output of our Build directory, usually usually you do in a share formatted\\SERVER\SHARE\BUILD.

In this case, we also have that option, although I do not think that anyone open this door to the world. The best seems to be that if we configure the output of the Build directly in Source Control, we buy cholón space in SC, but well… for that is.

image

What happens with my custom build templates?

As the Build Controller and Build Agent concept remains the same, because it isn’t to change us much the way in which we work if we have customized our Build templates. Simply access the configuration of the Build Controllers and already we can continue working as before.

image

There is trap a?

Yes, although in reality it is not trap. For example, you can make a template of Build to mount a specific environment to build a solution (e.g. registering COM components, prior to the compilation). But of course, as the AZURE VMs "have no State", because you will lose these changes when you refreshed them.

Although as the build runs where we need it, because we can return to this state when we need it… Risa

This point remains to be seen because I understand that it will be an environment more like a Sandbox to which we have access from the final version.

Now to migrate a couple of templates custom Avanade Spain to TFS AZURE, forgiveness to Team Foundation Service and prepare the next post.

Saludos @ La Finca

El Bruno

image image image

Sources:

http://blogs.msdn.com/b/bharry/archive/2012/03/27/announcing-a-build-service-for-Team-Foundation-service.aspx

http://geeks.Ms/blogs/devnettips/archive/2012/03/29/creaci-243-n-de-una-build-con-el-Nuevo-servicio-de-builds-para-TFS-service.aspx

http://blogs.msdn.com/b/visualstudioalm/archive/2012/03/27/build-on-the-Team-Foundation-service.aspx

[#VS11] Algunos puntos a tener en cuenta cuando trabajamos con el nuevo Team Build para Team Foundation Service

image

Buenas,

hace unos días Brian Harry hizo pública la noticia donde comentaba que ya podemos contar con un servidor Team Build en nuestro servicio de Team Foundation Service. Dicho de otro modo, esto significa que tenemos a nuestra disposición un servidor Team Build en TFS en la nube. Just great !!! (El amigo Vincenc también ha escrito un post al respecto)

Esto tiene muchas grandes ventajas, pero también tenemos que tener en cuenta varias cosas para trabajar con este modelo.

image

Importante: No tenemos acceso a la máquina física de Team Build

Esto significa que no podemos modificar nada en la misma para que nuestros proyectos compilen, ejecuten pruebas unitarias, etc. en este servidor. Personalmente pienso que esto es genial, un proyecto de software debe poder ser compilado y empaquetado solo a partir de los contenidos que se encuentren en el repositorio de Source Control.

Si utilizas componentes COM, o trabajas con un entorno de compilación que te requiera instalar algo en el mismo para poder compilar, pues tendrás que revisar tu modelo de desarrollo para poder utilizar Team Build en Team Foundation Service.

Inicialmente la VM de Team Build solo tendrá instalado

- Visual Studio 2010 SP1

- Visual Studio 11 Beta

Java por ahora nada de nada … aunque claro, estará en el paquete final, ya que los clientes de ECLIPSE con Maven 2 y Maven 3 lo necesitan.

Yo he hecho la prueba del “Hola Mundo” para Team Build en 10 minutos y funciona genial, aunque si en lugar de MSTests utilizas XUnit o NUnit, pues tienes que dedicarles unos minutos a la configuración.

Finalmente, un detalle interesante. Cuando definimos el directorio de salida de nuestra Build, usualmente lo solemos hacer en un share con formato \\SERVER\SHARE\BUILD.

En este caso, también tenemos esa opción, aunque no creo que nadie abra esta puerta al mundo. Lo mejor parece ser que si configuramos el output de la Build directamente en el Source Control, consumiremos espacio a cholón en el SC, pero bueno … para eso está.

image

¿Qué pasa con mis plantillas de build personalizadas?

Como el concepto de Build Controller y Build Agent sigue siendo igual, pues tampoco es que nos cambie mucho la forma en la que trabajamos si hemos personalizado nuestras plantillas de Build. Simplemente accedemos a la configuración de los Build Controllers y ya podremos seguir trabajando como antes.

image

¿Hay trampa?

Pues sí, aunque en realidad no es trampa. Por ejemplo, te puedes hacer una plantilla de Build que se encargue de montar un entorno específico para poder compilar una solución (por ejemplo registrando componentes COM, previos a la compilación). Pero claro, como las VMs de AZURE “no tienen estado”, pues perderás estos cambios cuando se refresquen las mismas.

Aunque como la build se ejecuta siempre que lo necesitemos, pues podremos volver a tener este estado en cuando lo necesitemos … Risa

Este punto está por verse porque entiendo que será un entorno mucho más parecido a un Sandbox al que podremos tener acceso desde la versión final.

 

Ahora a migrar un par de plantillas personalizadas de Avanade Spain a TFS AZURE, perdón a Team Foundation Service y a preparar el próximo post.

 

Saludos @ Home

El Bruno

image image image

Fuentes:

http://blogs.msdn.com/b/bharry/archive/2012/03/27/announcing-a-build-service-for-team-foundation-service.aspx

http://geeks.ms/blogs/devnettips/archive/2012/03/29/creaci-243-n-de-una-build-con-el-nuevo-servicio-de-builds-para-tfs-service.aspx

http://blogs.msdn.com/b/visualstudioalm/archive/2012/03/27/build-on-the-team-foundation-service.aspx

[# KINECTSDK] The future of the Kinect SDK

image

Buenas,

from the official blog of Kinect for Windows, comment on a couple of interesting details on the new version of the SDK of Kinect.

We go with the most interesting points

  • The next version will be 1.5, which is not a Major Release, but an evolution from the 1.0 version.
  • The date of departure will be at end of May.
  • Incorporating new languages for the recognition of voice, French, Spanish, etc….
  • The interesting thing is that partial skeleton with 10 points or more will be detected, they allow us to detect the upper part of a body.

I guess it will be part of something bigger, but it looks good.

Saludos @ Home

El Bruno

image image image

Source: http://blogs.msdn.com/b/kinectforwindows/archive/2012/03/26/what-s-ahead-a-sneak-peek.aspx

[#KINECTSDK] El futuro del SDK para Kinect

image

Buenas,

desde el blog oficial de Kinect for Windows, comentan un par de detalles interesantes sobre la nueva versión del SDK de Kinect.

Vamos con los puntos más interesantes

  • La próxima versión será 1.5, con lo que no es un Major Release sino una evolución desde la versión 1.0.
  • La fecha de salida será a final de mayo.
  • Se incorporan nuevos lenguajes para el reconocimiento de voz, French, Spanish, etc. …
  • Lo más interesante es que se detectarán skeleton parciales con 10 puntos o más, que nos permitirán detectar la parte superior de un cuerpo.

Supongo que será parte de algo más grande, pero tiene buena pinta.

 

Saludos @ Home

El Bruno

image image image

Fuente: http://blogs.msdn.com/b/kinectforwindows/archive/2012/03/26/what-s-ahead-a-sneak-peek.aspx

[# VS2010] New date of expiration for the virtual machines of Visual Studio 2010 ALM

image

Buenas,

those who are still using the virtual machine Visual Studio 2010 ALM for demos and testing, we have the good news that the expiry date of the same has been extended from April 9 to September 10, 2012, 2012. Risa

Download data can be seen from http://elbruno.com/2012/03/02/vs1-maquinas-virtuales-para-probar-visual-studio-11-alm-y-visual-studio-2010-alm/

Saludos @ Home

El Bruno

image image image

Source: http://blogs.msdn.com/b/briankel/archive/2012/03/27/updated-visual-studio-2010-alm-virtual-machine.aspx

[#VS2010] Nueva fecha de vencimiento para las maquinas virtuales de Visual Studio 2010 ALM

image

Buenas,

los que seguimos utilizando la máquina virtual de Visual Studio 2010 ALM para demos y pruebas, sabemos que dentro de unos días se nos acaba el período de prueba.

Por suerte el gran Brian Keller, nos confirma en un post que que la fecha de expiración de la misma se ha extendido desde el 9 de Abril del 2012 al 10 de Septiembre de 2012. Risa

Los datos de descarga se pueden ver desde http://elbruno.com/2012/03/02/vs1-maquinas-virtuales-para-probar-visual-studio-11-alm-y-visual-studio-2010-alm/

 

Saludos @ Home

El Bruno

image image image

Fuente: http://blogs.msdn.com/b/briankel/archive/2012/03/27/updated-visual-studio-2010-alm-virtual-machine.aspx

[# ALM] As 30 minutes a day can change your life

ALM 03

Buenas,

today is post of self-help. I’ve always thought that self-help books are created for people that do not fit or are not happy with what you have. Then these books describe a series of problems that is very likely that no one has, but clear the people endorsed them and… pum! editorial hit, you have millions of people buying a book that you basically repeated the lessons that you gave your parents when you were a teenager.

Although of course, it is better to stop €10 for a book that will help you, to take advantage of the wisdom which give you free there.

In my case, the 30 minutes is something that has cost me 35 years to learn. Some time ago, I commented as he personalized my own version of GTD, working with pomodoros of 25 minutes and managing my all with OneNote (link).Eventually, the fact devote periods of 25 or 30 minutes with an exclusive focus towards a single subject, has helped me to get things that previously could not.

But the most important thing I’ve learned, is that in these small blocks of time, I can achieve much, if I learn to separate the tasks that I’m adding in small blocks. Who writes so easily in 3 lines, then is far more complicated to implement when you take it to reality. But over time, you learn to distinguish large small stones stones; and finally you get are all small stones.

Note: do not know the history of rocks and the Lake of Toyota? because you should (link ))

This is beside the point that my father of guy, always told me that the best way to embark on a journey is taking a first step. Or if I forward my have a very big problem, so it’s best to separate into small problems. And then go to solving one by one. Come on it was free information he could have free and after study on ALM for more than 10 years, him I’m capturing the idea.

Note 2: my father is an engineer and is a crack if you did not know (link). In the next photo you see as the next generation of also has understood things better enter hammer blows to the head Risa

image

Then, what should I do with this to improve my development lifecycle?. Apply common sense and devote 30 minutes a day to find answers to the following questions:

  • I am developing quality software?
  • What can I do to improve the quality of my development process?
  • I’m working with the best tools?
  • I know how to work with these tools to be more productive?
  • I’m adding value to my business?
  • etc.

These wonder appear trivial, but for example the latter is one of the points that we abandon over the computer. Many times we think that the technological solution of the death is the best we can do, when in reality with something simple and concrete we are providing more value than we need. That Yes, while forgetting that "technical debt" (link) can destroy a project little by little.

To summarize:

It dedicates 30 minutes a day to think about how to improve your way of working.

Then apply another 30 minutes to implement these improvements.

You finally have a 30 minute session to assess whether these improvements are actually reflected in your day to day.

Beware, this is not a task for 90 minutes in a day, we distribute and thinking on how to improve with time… but thinking!

I do, and am also a daily pomodoro to

  • Make a CodeKata, to not forget about the foundations of programming
  • Read a little about technology, trends, etc., not to miss the train

Saludos @ La Finca

El Bruno

image image image