mylifeinaminute.com

Just got the message:

CodePlex Project Contributors,

**The information in this e-mail applies to project coordinators and developers that are using TFS with the Team Explorer client.  If you are using Mercurial or a Subversion client, then nothing will change for you**

During the upcoming weeks we will be migrating all of the CodePlex TFS projects onto our new TFS 2010 servers.  This upgrade will allow us to support new TFS features and provide increased server performance and reliability.  The move will happen on a server by server basis, so expect each TFS server (TFS01 to TFS10) to be down for a few hours as data is migrated.  Updates on when each server will be offline and an estimate on when they will be back online will be posted on our system outage page: http://codeplex.codeplex.com/wikipage?title=System%20Outage%20Report.

As part of this migration, the URL of your TFS server will change and this will require you to update your projects source control bindings.  After your project has moved, instructions on how to connect with Team Explorer to the new TFS server can be found on the source control tab of your project under “Source Control Setup”.  For detailed instructions on updating your source control bindings see:http://codeplex.codeplex.com/wikipage?title=Updating%20Your%20TFS%20Source%20Control%20Bindings.  Additionally, if you connect to your project using Visual Studio Team Explorer 2005, you will need to install the 2005 forward compatibility pack: http://www.microsoft.com/downloads/details.aspx?FamilyID=22215e4c-af6f-4e2f-96df-20e94d762689.  If you connect using Team Explorer 2008, you will need to install the 2008 forward compatibility pack: http://www.microsoft.com/downloads/details.aspx?FamilyID=cf13ea45-d17b-4edc-8e6c-6c5b208ec54d.

Finally, the TFS 2010 upgrade process checks two build templates files into your project under \BuildProcessTemplates.  These templates can be removed safely as we currently do not support TF build.

Thanks,
The CodePlex Team

It looks like it’s going to be time to install some forward compatibility packs.

One of my pain points as a SharePoint “administrator” is having to deal with deployments of solution packages to my environment without the best change management. This means that I often see packages making their way in to the environment without any thought given to keeping the package in case it needs to be reapplied at a later time (Note: I’m not the only one who controls what goes into the environment).

The solution? I whipped up a Windows application so download one, several, or all of the solution packages currently stored in the farm configuration database.

I have posted the application to CodePlex @ http://spsolutiondownloader.codeplex.com/.

The application must be run in the context of a Farm Administrator (i.e. right-click, Run As…) on a server in the farm for which you wish to download the solution package(s) from and requires the .NET Framework 3.5.

I would love some feedback from the community as to whether or not this useful. I have some other little apps in mind I could put together with the proper motivation.

zevenseas has released their SharePoint LifeCycle Management solution to CodePlex.  The LifeCycle Management solution can be used to track unused SharePoint sites as well as capture and automatically back-up sites.  Actions can be defined to use against your unused sites, such as emailing the site owner, locking the site, or even deleting it.

What are you waiting for?  Go check it out!