Buenas
Aqui dejo la presentación del evento de ayer sobre reporting con Team Foundation Server 2012.
Descarga la VM para probar en vivo los informes desde
http://blogs.msdn.com/b/briankel/archive/2013/04/17/list-of-all-visual-studio-alm-virtual-machines.aspx
Greetings @ Seattle
The Bruno
Good,
once more MSDN Latin America friends invite me to participate with them in a 60-minute webcast. In this case it is to discuss options of reporting offered by Team Foundation Server 2012 (and some Team Foundation Service).
The event is June 18 in WebCast format, and they can register at the link below.
Registration: https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032551096 & Culture = en-AR & community = 0
Saludos @ Málaga
El Bruno
 |
 |
 |
Buenas,
una vez más los amigos de MSDN Latinoamérica me invitan a que participe con ellos en un webcast de 60 minutos de duración. En este caso es para comentar las opciones de reporting que ofrece Team Foundation Server 2012 (y algo de Team Foundation Service).
El evento es el próximo 18 de junio en formato WebCast, y se pueden registrar en el link de debajo.
Registro:
https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032551096&Culture=es-AR&community=0
Saludos @ La Finca
El Bruno
|
|
|
Hola,
In addition to the news that will be Visual Studio 2013 hand and Team Foundation Server 2013, there is one very interesting which is available at Team Foundation Service Although only try with Vs2013: the ability to perform Load Tests using Team Foundation Service . For example, when today we edit a configuration file for the execution of tests see options in VS2012.
Visual Studio 2013 adds one more than interesting option: the ability to run these tests using the cloud (Team Foundation Service )).
Then once configured and executed them, we can see the results directly as if it were in local
Obviously for reasons of availability, you can not run all the tests in the world now in Prerview mode, it will be limited to a quantity of executions and load X. If it will be possible to what use the feature with an extension to VS2012 or with the preview of Visual Studio 2013. because that… now to wait for the June 26 Build to try this also 
Saludos @ La Finca
El Bruno
|
|
|
Buenas
Además de las novedades que llegarán de la mano de Visual Studio 2013 y de Team Foundation Server 2013, hay una muy interesante que está disponible en Team Foundation Service aunque solo puedes probar con Vs2013: la capacidad de realizar Load Tests utilizando Team Foundation Service. Por ejemplo, cuando hoy editamos un archivo de configuración para la ejecución de tests vemos las siguientes opciones en VS2012.
Visual Studio 2013 agrega una opción más que interesante: la capacidad de ejecutar estos tests utilizando el cloud (Team Foundation Service).
Luego una vez configurado y ejecutados los mismos, podremos ver los resultados directamente como si fuese en local
Obviamente por cuestiones de disponibilidad, no podrás ejecutar TODOS los tests del mundo por ahora en el modo Prerview, estará limitado a una cantidad X de ejecuciones y de carga. Lo que si será posible es utilizar la feature con una extensión para VS2012 o con la preview de Visual Studio 2013. pues eso … ahora toca esperar al Build el 26 de Junio para poder probar esto también
Saludos @ La Finca
El Bruno
|
|
|
Hola,
continue with the short week of new features in Web Access from Team Foundation Service . Today we are going with one that surely will draw a large ulcer “purists”: Lightweight code commenting; It is the ability to add comments “inline” within the code, in a collaborative manner. For example, from the section of code in Team Foundation Service, we can access a changeset, see changes in a file, and a specific line, add a comment, for example.
The partnership model is much better reflected official TFS support example:
I.e., instead of talking with people, this model can have to comment and review code model not “online”. Surely a more than they hurt teeth with this, however I’m seeing comments that leave me from Bangalore / Seattle and distributed environments is a light which does not require a full process of “Code Review” 
Source:
http://tfs.visualstudio.com/news/2013-jun-3
Saludos @ Home
El Bruno
|
|
|
Buenas,
sigo con la semanita de new features en Web Access de Team Foundation Service. Hoy vamos con una que seguramente sacará una úlcera de las grandes a los “puristas”: Lightweight code commenting; es la capacidad de agregar comentarios “inline” dentro del código, de una manera colaborativa. Por ejemplo, desde la sección de código en Team Foundation Service, podemos acceder a un changeset, ver los cambios de un archivo, y en una línea específica agregar un comentario, por ejemplo.
El modelo de Colaboración queda mucho mejor reflejado en el ejemplo de la ayuda oficial de TFS:
O sea, que en lugar de hablar con las personas, puedes tener este modelo para dejar comentarios y revisar código en modelo no “online”. Seguramente a más de uno le dolerán los dientes con esto, sin embargo yo estoy viendo comentarios que me dejan desde Bangalore / Seattle y en entornos distribuidos es una opción light que no obliga a un proceso completo de “Code Review”
Fuente:
http://tfs.visualstudio.com/news/2013-jun-3
Saludos @ el hotel del los colorines
El Bruno
|
|
|
Buenas,
continue with the updates that have been implemented “by-the-face” in Team Foundation Service the name of the new Visual Studio 2013. Today we will see the “Features“. While the assistance of Team Foundation Serviceexplains it a very scientific way, a way to describe a Feature is to think at a higher level than GDP.
In my case, today when I speak with Stakeholders or product owners of my projects, soil create PBIs to leave evidence of the same in my TP. What happens is that these PBIs tend to have a “mental smoke” very high level, what we usually do is to then create real PBIs then we break down in real TASKs in implementation, etc etc etc…(not tell you anything that you don’t know). Now, a Feature comes to represent the top level of abstraction that allows us to have a “repository of ideas” that can then be defined at a more detailed level as a TP PBIs. A good thing having the Features is that they are common to all the TPs for a Team Project Collection, so you can organize them at the organization level and then to reach specific levels of each project.
Turning to the implementation of this “feature”, we can see in the home of our backlog
Once a Feature has all the properties of a WorkItem, title, description, area, Tags, it is possible to handle it on a Board, kanban, etc.
It is then possible to define the type of deployment that you want to do, for example with a related GDP.
Once you have defined the implementations, because we can have a hierarchical view of Feature / / GDP
That by today, morning news.
Source:
http://tfs.visualstudio.com/news/2013-jun-3
Saludos @ Eventazo en Madrid
El Bruno
|
|
|
Buenas,
seguimos con los updates que se han implantado “by-the-face” en Team Foundation Service con la excusa del nuevo Visual Studio 2013. Hoy veremos las “Features”. Si bien la ayuda de Team Foundation Service lo explica una forma muy científica, una forma fácil de describir a una Feature es pensar en un nivel superior a un PBI.
En mi caso, hoy cuando hablo con los Stakeholders o product owners de mis proyectos, suelo crear PBIs para dejar constancias de las mismas en mi TP. Lo que pasa es que estos PBIs suelen tener un nivel de “humo mental” muy alto, lo que solemos hacer es crear luego PBIs reales que luego desglosamos en TASKs reales de implementación, etc etc etc … (no te cuento nada que no sepas). Ahora bien, una Feature viene a representar ese nivel superior de abstracción que nos permite tener un “repositorio de ideas” que luego se pueden definir en un nivel más detallado como PBIs de un TP. Una cosa buena que tienen las Features es que son comunes a todos los TPs de una Team Project Collection, con lo que puedes organizar los mismos a nivel organization y luego llegar a los niveles específicos de cada proyecto.
Volviendo a la implementación de esta “feature”, la podemos ver en el home de nuestro backlog
Una vez creado una Feature tiene todas las propiedades de un WorkItem, título, descripción, área, Tags, es posible manejarlo en un tablero kanban, etc.
Luego es posible definir el tipo de implementación que se quiere hacer, por ejemplo con un PBI relacionado.
Una vez que tienes definidas las implementaciones, ya podemos tener una vista jerárquica de Feature // PBI
Eso por hoy, mañana más novedades.
Fuente:
http://tfs.visualstudio.com/news/2013-jun-3
Saludos @ La Finca
El Bruno
|
|
|
Hi,
yesterday I commented that in TechEd 2013 they were announcing new features to the new version of Visual Studio 2013. The interesting thing is that at the same time are announcing these changes, some updates were made in vivo envelope Foundation Service Team (basically because in 20 days we have the new Beta of Visual Studio 2013 to begin work).
If yesterday were working with Team Foundation Service , surely you will have given you some headache, response times were slow, however you may have also noticed that there was some new features available, some very interesting, for example the ROOMS. Under all the elements in the home of your Team Project, you can see the access to them.
Then with one click, you walk into the Room, and you can start see everything that happens on your computer.The following image shows an example, where it is possible to see as I entered and left the Room a couple of times.
Among the options you can find in the Room, you have the concept of events to validate that information is the same. The events correspond to the categories of
It is also possible to define the users or groups of Team Foundation that we want them to be part of the Room.
Good and after seeing all this, comes the question of rigour Would why ROOM? Maybe because from the activity of your computer, you can have a feedback and constant conversation of what happens in it. For example, after accommodate and reschedule a couple of WorkItems, I can comment in the CHAT of the ROOM why this change (in this case is a Brown hides because we are left without a team). I mention in the chat and then chat people can view and comment on it.
Taking advantage of the capabilities of the GROUP chat is possible references to a member of the team with the @ front or to a WorkItem with #. In the following image you can see to the Edu, what you enjoy most with the Rooms at this time,.
It is also possible to see how many people are in a Room, directly from the home
Finally a couple of interesting facts about the Rooms
We will the idea is very good and should give you a bit of time to see if the team adapt to it.
And a little help, because you have already updated the help of TFS
http://tfs.visualstudio.com/en-us/learn/collaborate-in-a-team-room
Saludos @ La Finca
El Bruno
|
|
|
