If like me, you also have the tendency to forget (*not that I wish for it*) the version numbers before and after SP1 is applied, here is a little visual help for all of us.
Original release version of Windows SharePoint Services 3.0 is 12.0.0.4518. This applies to both WSS and MOSS installations – Remember, MOSS is built on the top of WSS.
Updated version of Windows SharePoint Services 3.0 after SP1 is installed is 12.0.0.6219.
If you are going to install a clean WSS from the scratch either on 2003 or 2008, I would highly suggest you to go for WSS with SP1 Slipstream. It can be downloaded for both 32 bit and 64 bits.Update: You’ll see slipstream bits for MOSS SP1 in the next few weeks.
Configuration API introduced in .NET 2.0 gave us whole bunch of options to read and update configuration files such web.config and machine.config files. A very useful framework if you want to dynamically interact with configuration files as they apply to your web applications. WebConfigurationManager possesses all the knowledge of the web.config object model and provides full access to it. The Question is : Can I use this API to access and change web.config files associated with my SharePoint apps? Yes , you certainly can, but you have to keep track of the changes , support the ability to roll them back and more importantly in a farm installation where your app is scaled across multiple web front end servers , your code should be able to reach out to those servers and apply changes (Add/Delete/Update). Although it is not impossible to do it this way, it’s simply more convenient if WSS Object Model could take care of this for us.
Conveniently, WSS object model offers a new class this time around which allows your code (that is within your Feature event receivers , console apps or custom installation applications) to dynamically make and propagate changes to web.config files across your farm using SPWebConfigModification class (Microsoft.SharePoint.Administration namespace). You have the option to add/modify/delete sections, child elements and attributes with some limitations and through many workarounds! We will take a look at some of the issues and workarounds (if there is any:)) in this post. Read more…
Since TFS 2008 came out , I have always wanted to find sometime to dive into this. I am pretty slammed these days with many things – work,life, shopping and shoveling the snow- Just kidding
Actually , I hired someone to take care of the shoveling task, therefore I can save sometime to work on other things such as TFS 2008 – what a geeky life man . Anyway, I finally got this up and working and I decided to create a very high-level walkthrough of the things I did. Fortunately,this time Installation process and best practices are fairly well-documented from the beginning so I just linked to them wherever needed.
In this white paper , I will go over the advantages of using virtualized development environments for your WSS and MOSS 2007 projects using virtual Server or Virtual PC. I will be demonstrating how you can leverage differencing drivs feature in these two great products to build client-specific dev environments with exclusive customizations and in a completely isolated fashion.
Microsoft locked in the dates for 2008 wave launch of Windows Server 2008, SQL Server 2008 & Visual Studio 2008 .Launch is the full blown typical launch event (partners, community zone, technical readiness presentation) and please keep in mind that these dates are the lunch dates only not Release To Manufacturing (RTM) dates.
Technical Readiness is just like any other Technical TechNet tour, with a three session presentation. Community Connection events are interactive workshops which will look at some of the core changes that are occurring from a technology, industry, community and career perspective – sharing experiences and connecting you with key individuals in your community to support your plan.You can also visit the official web site below and make sure you subscribe to the RSS feed for updates and more information. http://blogs.msdn.com/ridethe2008wave/default.aspx
. Anyway, I finally got this up and working and I decided to create a very high-level walkthrough of the things I did. Fortunately,this time Installation process and best practices are fairly well-documented from the beginning so I just linked to them wherever needed. 
tfs.pdf
