Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Looks like you're trying to connect to the tfspreview from the TF.EXE command of Visual Studio 2010, right ?</p> <p>Even if you installed the QFE to enable TFSPreview access in Visual Studio be aware that this is mainly a "limited patch" and that TF.EXE is not fully compliant with TFSPreview.</p> <p>You should install the VS11 beta and use the TF.EXE from this version, maybe you'll be more lucky.</p> <p>Btw I see you're determined to create a schedule job to backup TFSPreview sources. You have to know that even if the platform is in preview state your whole Team Project Collection will be kept 3 months after the TFSPreview gets RTM and you'll be notified several time of the possibility to:</p> <ol> <li>Upgrade to the "paid version"</li> <li>Retrieve the Team Project Collection in local before it's destroyed from the MS servers.</li> </ol> <p>Brian Keller from MS was very clear about that. So don't be afraid to loose your code.</p> <p><strong>Update:</strong> <a href="http://blogs.msdn.com/b/bharry/archive/2012/03/27/announcing-a-build-service-for-team-foundation-service.aspx#10288158" rel="nofollow">Comment</a> from Brian Harry (one of the TFS Big bosses):</p> <blockquote> <p>Brian Harry MS 27 Mar 2012 1:06 PM That said, let me repeat a few things I've said before:</p> <p>1) Our goal is to be cost competitive with the market for similar capabilities.</p> <p>2) I mentioned in my CodePlex post the other day that we envision a unified service across TFSPreview/CodePlex that scales from free to paid - details still to be determined there.</p> <p>3) <strong>Before we institute any billing model, we will provide a high fidelity and easy way to migrate your data from the cloud to an on-premises TFS server should you decide that's more economical</strong>.</p> </blockquote> <p>Feel free to contact Brian on his blog to ask him a confirmation, he always answers to people.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload