A small post to inform you that the beta of Team Explorer Everwhere 2010 SP1 was released and can be downloaded here:
If you don’t know what Team Explorer Everywhere 2010 is, it’s the client Team Explorer for Eclipse! (previously know as TeamPrise before being bought by Microsoft).
Here are the addition of the SP1:
- Complete support of localization.
- Support for Gated-Ckeckin with the same user experience as in Visual Studio 2010.
- Support for Private Builds.
- Build explorer enhancements (icons).
- Support for rich editing in WorkItem.
- Support for Apple Keychain and Gnome Key Ring to store local TFS credentials.
- Support for custom control in WorkItem (only for desktop client).
- Support for Internal Merge in Eclipse.
- Enhancements on “Synchronization perspective” interface.
- Enhancements on Shelve interface.
Yesterday was the keynote of PDC 2010. I could not attend the broadcast, so I’ll just relay an important information without going into details:
Team Foundation Server will arrive on Azure!
For more information, please read the post from Brian Harry
(English) or from Vincent
Yesterday was the keynote of PDC 2010. I could not attend the broadcast, so I’ll just relay information important enough without going into details: Team Foundation Server will arrive at Azure! For more information, please read the post from Brian Harry (English) or that of Vincent (in French). Carpe Diem.
As promized her is a sample of how i’m using the UpdateAssemblyInfo activity i’ve published on codeplex.
First let’s describe what we want:
- Increment the build number of my AssemblyFileVersion automatically for all the projects in a solution when doing a build. The major and minor versions of the AssemblyVersion and AssemblyFileVersion must not change and the revision number must be 0.
- Don’t modify the solution sources in TFS and let the developers do what they want.
- The BuildNumber of my build must contains the AssemblyFileVersion so that my build name, label and drop location are easily identifiable.
- Don’t modify the version numbers when doing a gated checkin or a private build.
- Be able to launch a build and specify to skip versionning.
Before updating our build template i’ll start by configuring my solution to make easier the versionning of all the projects. Let’s add a GlobalAssemblyInfo.cs (or .vb if you use VB.Net) file to the solution as a solution item:
read more →
Brian Harry just annouced on his blog that the Developer Division has made successfully it’s first end-to-end build of all Visual Studio using TeamBuild 2010. Here’s an other proof that it’s a great product.
As Brian says, Microsoft will now be able to test and find missing features to add for future versions.
I’ve published on codeplex an activity which provides a way to manipulate the AssemblyVersion and AssemblyFileVersion values of AssemblyInfo files at build time under TeamBuild 2010: UpdateAssemblyInfo.
This activity supports the use of a pattern to specify how to update the AssemblyInfo files versions. the following tokens are dynamically replaced during execution:
- $(current): uses the current value.
- $(increment):increments the current value.
- $(date<format>): uses the current date formatted with the specified <format>.
- An integer: forces the value to the specified value.
The specified pattern must respect the version numbers form “A.B.C.D”. As an example, the pattern “$(current).$(current).$(increment).0″ keeps the current major and minor version, increments the build number and forces the revision to 0.
I’ll post an entry on an example of how to integrate this activity soon but for now i’ll recover for those past days heat (and the lack of sleep which goes with it :)). Stay tuned!
After showing you how to customize IntelliTrace, i’ll show you today how you can create your own graph dependency analyzers for VisualStudio 2010 architecture tools.
Before starting here is another warning (still in bold and red so everyone sees it ):
Microsoft does not give any documentation or support on all that i will explain because even it’s possible, the functionality is not supported.
Now that you are warned lets start implementing a small analyzer which will show us all nodes starting with “Qetza.”.
First we create a class library and add the following assembly references:
These assemblies are in the sub directory “Common7\IDE\PrivateAssemblies” of your VisualStudio 2010 install directory (by default “C:\Program Files\Microsoft Visual Studio 10.0″).
read more →
I’ve published on codeplex a small command-line tool to administer work item queries: wiqadmin.
This tools, compatible with TFS 2008 and TFS 2010, supports the following commands:
- List queries.
- Export a query.
- Import a query.
- Rename (and/or move under TFS 2010) a query.
- Delete a query (or a folder under TFS 2010).
The TFS 2010 version supports folders
This post is part of a series on TeamBuild 2010:
It’s time i get back to my presentation of TeamBuild 2010 new features
Since TeamBuild is now based on Workflow Foundation 4.0 Microsoft has provided some activities specifically for TeamBuild. Those activities are like the Task in TeamBuild 2008 :
read more →
Today i’ll show you how to customize IntelliTrace in VisualStudio 2010 so that you can trace events from your own methods. But first some warnings (in bold and red so no one misses them ):
Microsoft does not give any documentation or support on all that i will explain. There is also a chance that the way you can customize IntelliTrace will be revamp in the next version of VisualStudio (which might explain the lack of documentation and support).
Now that you’re warned let start and see how we can customize IntellTrace so that we can trace our own method calls! I’ll be using the following class for this post:
read more →