Bonjour à tous,
La nouvelle CTP d'Octobre de Visual Studio 2010 vient juste de sortir, je vais donc en profiter pour faire une petite série de post sur mon blog pour parler des nouvelles fonctionnalités.
Il y a plein de « Walkthrough » fournit avec cette CTP, je trouve ca super, mais dans ma série de post je m'efforcerais de présenter les nouvelles fonctionnalités en me basant sur ma propre expérience d'utilisation de l'application.
Pourquoi, les raisons ne manquent pas :
- Ca ne sert à pas grand-chose de blogger sur ces Walkthrough, d'autres vont certainement le faire…
- Ne pas utiliser les exemples de Microsoft me permettra de poussez la bête un peu plus loin.
- J'suis vieux jeu, j'aime bien découvrir les choses par moi-même !
Donc je vais découvrir ces nouvelles fonctionnalités et je ne manquerais pas de les partager avec vous. Voir si certaines frustrations sont enfin disparues, si les fonctionnalités que l'on attendait pour 2008 sont enfin présentes et les fonctionnalités qui seront de nouvelles bonnes surprises.
We are all interested about the new killer features in the Architect version, the typed links in Work Items, the editable Workflows in Team Build, and so on.
But we still have to remember that at both at the beginning and the end of the day we have to work with Configuration Management.
The source control of Team System was already good at the very beginning, but for a platform that as for only purpose to be the ultimate ALM product, you must have an excellent one!
Things I miss in TFS 2008:
1) Hard to determine the relationship between branches, the time notion was unusable. You can see what is created from what, but not much more. Lacking of graphical representation.
2) Three ways merge only possible from directly related branches, forcing you to do a baseless merge in other cases.
3) Merge/conflict resolution still not as good and intuitive as it could.
So I’m going to see what changes for these things.
I’m creating a new Team Project called “Test_SCM”, using the Agile Process Template.
Inside $/Test_SCM I create a Main folder, aimed to be a main branch, and then check it in. After I create an “out-of-the-wizard” Winforms application called WinformApp, child of the Main folder and do another check-in.
So far things look like:
Playing a bit with the Source Control, you quickly realize that there’s now a distinction between folders and branches!
The first and most obvious is on the display, a branch has now its own icon, makes you identifying one much quicker than before.
At any time you can convert a given folder to a branch, there’s a new sub-menu Branching and Merging in the contextual menu of the Source Control Explorer:
From this menu you can:
- Create a new branch from the current one.
- Merge changesets from one branch to another. (Nothing new so far…)
- View the Hierarchy related to the current branch, sounds like fun! J
- Convert the folder to a branch. Warning: this doesn’t lead to a pending changes, but to an instantaneous conversion, and apparently currently irreversible!
- Revert a Branch back to a folder (I couldn’t achieve this, the menu item is always disabled).
- Reparent a Branch, sounds like changing the parent of a branch, again, I couldn’t do it, the menu item being always disabled.
Now the weird part: you can create a branch from a folder: this will end with two…folders!
See the pictures below, I have two branches: Main_2 and Main_2_V2, but they’re displayed as folder, and looks like it would have been different if it was branches, see after.
Your Properties dialog is different for a Folder and a Branch item. For the Folder you have exactly the same dialog as for the 2008.
For a Branch, a new dialog appears:
The Relationships tab is a bit more sophisticate than for a “branch folder”:
So what’s the point of all of this, why two kinds of branches? Well, my guess is there’s now a change in how branches are handled, and for the sake of backward compatibility you still have the old model, coexisting with the new. Looks like I’m going to talk with Microsoft people on this one.
I found out a new limitation: either you’re using a branch or a “folder branch”, you can’t create a new branch from it that is physically stored inside it!
For instance:
$/MySoft_Main
$/ MySoft_Main/MySoft_Version_1_0 ß Can’t happen if you want MySoft_Version_1_0 to be a branch created from MySoft_Main!
This was totally possible in previous version, and now this is something you can’t do anymore.
Hi everybody,
The October CTP of the now called Visual Studio 2010 just went out, so I’m taking advantage of that to start a little series of posts about the new features of Rosario.
There are many walkthroughs delivered with this CTP, and I really think it’s a cool thing, but in this series, I will demonstrate features based on personal experimentation only.
The reasons are simple:
- There’s no point to go through the walkthroughs, well, I guess…
- Not using the Microsoft’s samples and cases will allow me to challenge the release better.
- I simply want to discover the release from scratch, old habit, old fashioned guy?
So, the purpose is to discover the new values of Rosario and share it with you guys, challenge it a bit, see what frustrating things are gone, what missing features and wished stuffs was added and how.
Let’s start with the very first thing in application development: coding! :)