October 2008 - Posts
A good video from PDC that outlines what is in the works for ASP.NET 4.0
http://channel9.msdn.com/pdc2008/PC20/
If you are interested in getting some of the latest bits then you may want to take a look over here
http://www.codeplex.com/aspnet
If you are interested in getting the .NET 4.0 poster, here you go...
I saw this on Brad Abram's blog
Deep zoom version
PDF Version
If you run any of these OS( Windows Vista RTM, Windows Vista SP1, Windows Server 2008 )and need to get your PC all set up for doing web development then you may want to take a look at these 2 Beta products that are now available
Microsoft Web Platform Installer - Installs IIS, Visual Web Developer 2008( express edition) , SQL Server 2008 (Express edition) and the .NET Framework. It also allows you to pick and choose the components you want installed.
Microsoft Web Application Installer - Allows you to install commonly used applications like .NET Nuke,Graffiti etc to name a few
I definitely like this concept and I am sure it sure simplifies the install experience. I would definitely like to see a version for Windows XP too :-)
TFS does a great job of automating build. With out having to mess with msbuild , it will pull all the source code from source control, do the build label the build in source control etc. In our scenario we did not want TFS to label each and every build, but only builds that were of production quality. To turn off labelling in TFS build set the property SkipLabel to true like below
<SkipLabel>true</SkipLabel>
We also have the option to override the label that TFS puts in. By default it looks something like this
[Name of build definition]_yyyymmdd.[running number of build for that day]
To override the default label, go ahead and add a Target called BeforeLabel and set the property for LabelName and LabelComment(Comments are optional, but its always good to have them ;-) . In our case , in the comments we add the information about who triggered the build, from which machine and at what time just for posterity sake
<Target Name ="BeforeLabel" >
<
Message Text="----Creating a source control label-----"></Message><CreateProperty Value ="Version-$(Version)">
<
Output PropertyName ="LabelName" TaskParameter="Value"/></CreateProperty>
<
CreateProperty Value ="Release Build Version -$(Version) at $(StartTime) initiated by $(RequestedBy) from $(MachineName)"><Output PropertyName ="LabelComment" TaskParameter="Value"/> </CreateProperty>
</
Target>
Some information on Vistual Studio 2010 aka Rosario and .NET Framework 4.0
From Channel9 , From the Microsoft Web site , From CRN
Also note that from October 1st all MSDN subscribers who get Visual Studio Team System Development edition will also get the Visual Studio Team System Database edition and vice versa... Nice !!!!
As a part of the team build process, if you need to check out and check in a file and do not want that to trigger a CI build then the easiest way is to put ***NO_CI*** in the comment during check in.Easier than that there is built in property $(NoCICheckinComment) that you can use
On finding find this string in the comment TFS knows that it doesn't need to trigger a build
More Posts