TFS Basic – continued…

I found some more info on TFS 2010 and the “Basic” version on bharry’s WebLog.

Lot’s of nice pictures there but I’ll skip right to the listed features of TFS 2010 Basic:
All of this gives you a development system with Version Control, Bug tracking and build automation (making continuous integration a snap!).  What it lacks from Standard TFS is Sharepoint and Reporting capabilities.  The great thing though is that TFS “Basic” IS TFS so as your needs grow you can reconfigure it to add more capabilities.

I’m guessing this will quickly become the most common setup. SourceSafe on steroids… while TFS Standard/Advanced will be SourceSafe on sci-fi steroids Ler

Advertisements

TFS Basic

Apparently support for SourceSafe is set to end in mid-2011. SourceSafe users need not worry, MS has you covered. With TFS 2010 there will be a “Basic” installation option which will allow you to installa TFS (or at least a part of it) on client OSes. Just like SourceSafe. Further more, the Basic version is supposed to be cheaper than the full TFS license.

Now, the only question is what features of TFS will be included in this Basic installation? My guess is source control only. Which is more than enough reason to move from SourceSafe to TFS Basic asap in my opinion.

Conversion Issues

Objective:
Get a VS2003 ASP.NET web application project from SourceSafe, migrate to VS2005 and add to TFS source control. All done on a PC running Windows Vista. As VS2003 will not run on Vista opening the solution in VS2003 and disconnect it from source control is not possible… might be possible to do from SourceSafe, but I decided to give it a go and just open it in VS2005 straight away.

Problem:
VS2005 conversion wizard fails to convert the web application. Depending on if I let the .sln file point to localhost or changed the projekt path to “C:\myAppPath\myWeb.vbproj” I get two different errors:

Error 1 (keeping localhost/myWeb/myWeb.vbproj as project path):
Conversion Issues – myWeb.vbproj
Thats it… No clue as to what is wrong.

Error 2 (changing to C:\myPath\myWeb.vbproj as project path):
Conversion Issues – myWeb.vbproj:
Unable to open the Web ‘C:\myPath\myWeb.vbproj’. The Web ‘C:\myPath\myWeb.vbproj’ does not exist.
Looks a bit more helpful, but since the file DOES exist… No, no more helpful than what I got in Error 1.

Solution:
As it turned out there wasn’t really anything wrong with the myWeb.vbproj file. Except that it was write protected… Checking the “make writable” checkbox when getting the code from SourceSafe (or just removing the write protection from the file) made all the difference. VS2005 disconnects the code from SourceSafe source control and converts everything Cool

Now I just need to solve all the compilation errors and the code will be ready to check into our TFS… Looking back, I might have been able to avoid the entire problem by following Microsoft’s instructions for migration. But why learn to swim when it is soooo simple to just jump into the deep end of the pool? Anyway, hope this is helpful to someone else…