[VNEXT] The next Visual Studio vNext (II)



We go with some of the innovations that are discussed in the TechEd on the new version of Visual Studio:

IntelliTrace in production

If you are using IntelliTrace already you can get an idea of the power that can have this tool if her activate in production for the detection of bugs in real time. Here me I do not forget to stress that this is “harmful”, that we should never look for Bugs in production, but when we have, better to have the best possible tools. The demos of the TechEd are very nice because they show a website, which you activated the IntelliTrace using PowerShell in 5 seconds, reproduces an error and then reads the historical trace of IT until you find the same. This in a real environment is much more complex, but hey, with time and the traces of IT well seccionadas, is a help.

New DashBoards in Team Explorer Web Access

Surely this is not the official name at the end, but this is one of the most anticipated advances because it includes features 100% oriented to agile project management work with Team Foundation Server. In the top menu of the WebAccess, we can see the accesses to the WorkItems, Source, Build, etc. we already know.


But the interesting at this point are the 2 new views of information that will be incorporated with vNext. For example, in the case of BackLog, in the same we see a quick glimpse of our ground floor, with the ability to quickly add items to it and also the view of the past, present and future work. Incorporate features very cool, as the order items directly with Drag & Drop, and then again with Drag & Drop, place the elements of the PB in the situation we want: past, present and future. Up to the right, it is possible to see a small chart with points of user that have been “used” in past iterations, compared with the available capacity, so that we can go to refine our concept of ability as we move forward.


Another view in the new Team Foundation Server Web App, is that we have to analyze and work with our Sprints. The following image shows how the following dashboard allows us to see in one fell swoop the current state of the elements of the Sprint, both User Stories as Tasks, and to see the workload for each of the members of the team. Once again in the Top-Right sections have different charts that show me my project-related information in real time. If for example, I see that the ability to work my team is in danger, I can drag a User Story in a future iteration and the data of the charts will be updated in real time.


If you are a fan of the boards and the PostIts, because this new view Boards surely you will like much. In the same we can decompose each of the User Stories of our PB in the tasks, and see the classical view of slate with the elements within it.At this point, the great ally is the Drag & Drop… Open-mouthed smile. There are rules to validate the elements, time of holidays, filters for people, etc. to expedite our work without having to play with Excel + VS for this work.


Team Navigator Panel

Another breakthrough is the new panel that also be a kind of direct access to Team Foundation work items, us allows to perform quick actions of CheckIn, review of Builds, status, etc. An interesting example of the TechEd, is a scenario where asked me an urgent modification to a file, and to not lose my current working environment, as it is recorded with a snapshot (or shelveset)make the change that I have requested and then I can go back to the same in 2 clicks.


Analysis to identify sections of Copy & Paste

A large number of problems in the development are taken for our beloved “Copy & Paste”, usually copies a portion of code to “make test” and from there, that code is live on forever, his “true home” desconectacto, etc. Come on, do not tell anything new. As well, vNext, incorporates a new tool that analyzes the code source looking for patterns of Copy & Paste (code Clones to be not so aggressive).


In addition to analyzing the complete code of a solution, it is possible to select a portion of code, that us “smells bad” and from the same search for duplicate code.


Code Review incorporated

Once more using the pane [Team Navigator] can take advantage of new features in Code Review that will be incorporated in vNext. For this, and based on the current work that we are doing, we create a task (is not a task of TFS) of Code Review and we share it with a coworker.


When our coworker receives the request for Code Review, it can access all the context information for this activity, including things as powerful as see the sections of code modified in the original state and the State to Code Review as shown in the following image.


From this moment, it is possible to make recommendations on classes, lines of code, etc., with a very interesting thread stops the cycle of development.

Customer Feedback Tool

We finally arrived at a version of Microsoft Test Manager in that they may provide their comments, suggestions, etc. on a specific product using this tool for end customers. as I understand, it works in offline mode, because it makes no sense open our TFS server to our customers and it is then possible to synchronize this information as a local data to process this feedback.


Greetings @ Here

The Bruno


Source: http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/FDN03

One thought on “[VNEXT] The next Visual Studio vNext (II)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.