Thanks to everyone who posted in this thread about my v1.5 vsts issue. I 
ended up deploying v1.6 to my PC and ran the last version I recently posted 
with the one vsts block and it runs fine with v1.6! I was able to force the 
build via the Dashboard and when I changed some source code in my TFS-2010 
repository it took off and brought down the source to my PC and did the 
build with no reported errors. I say it completed the build which is not the 
exact truth as I have not deployed Nant or the many other required libraries 
and such but what I needed was to prove we need to update to v1.6 by proving 
that instead of getting access errors from the TFS Server I can pull down 
the source elements which I now can with v1.6!
 
I am working as a SCM Architect on a very large enterprise size client that 
is making a move to TFS-2010 and our first phase is planned for doing the 
builds with the exisiting Cruise Control solution. Once we go live with 
TFS-2010 and builds continue with CCnet we will be busy taking all the 
Products and creating seperate TFS Projects out of the entire current SVN 
source tree. Then we will sunset the SVN box and move over to a complete TFS 
solution.
 
 
Thanks again for all your help!
 
 
 
-----mikeD

Reply via email to