At the end of October 2012, Microsoft announced the Team Foundation Service, not to be confused by Team Foundation Server (TFS).
This is essentially TFS online or TFS in the Cloud. You can create a unique URL for yourself and have 1 project up to 5 users for free. Any more of either and you have to pay extra for it. This will be a stable offering in 2013.

I have been looking for a source-control solution for some time now, and the only options were GitHub (paid for a private project, free for open-source) and BitBucket.atlassian.com (free, but you need a Git project). I do not want to manage a server, so Subversion or TFS was not an option.
In fact, BitBucket seems to be the only free option.

So, TF service was a welcome thing.
Note: The URL for it is: http://tfs.visualstudio.com and the old URL for tfspreview would be carried forward to this new one. The old URL will be deprecated. So, if you created your projects there, you will get them at the new URL.

Let’s say you want to delete a project you made. This is a no-no, as stated by the TFS team and they say a collection cannot be deleted. With a workaround, a Team Project can be deleted. This is not possible from the GUI (keep looking), but a simple command line command should do the trick.
To do this, go to the Visual Studio command prompt and let’s say you have a project called “foo” you want to delete. Type the command:
tfsdeleteproject /collection:https://foobar.visualstudio.com/defaultcollection foo

tfs capture

This deletes the foo project from the default collection. This is a complete hack and is insecure because no credentials need to be supplied. This also means that someone else could potentially delete your project, so be weary of this for now, and maintain a separate backup locally in case this happens and always think it could. I would expect this hole to be plugged in the near future, so don’t count on it to be there when you try..

http://blogs.msdn.com/b/bharry/archive/2011/09/19/deleting-a-team-project-from-the-team-foundation-service-on-windows-azure.aspx has this info.

Advertisements

Recently, I went to install the released Windows Phone SDK 7.1 for Mango and got a weird error while executing the installable vm_web.exe with a message box saying

Visual Studio setup cannot run in compatibility mode.
For more information see the ‘Installing’ section in the Visual Studio readme at http://go.microsoft.com/fwlink/?LinkID=143397.

Bah, this was humbug and I had VS Ultimate installed with all the latest service packs.

A little snooping around gave me a very simple solution.
Simply, copy your vm_web.exe to C:\ and run it from there. This worked like a charm.

Props to the post: http://blogs.msdn.com/b/astebner/archive/2010/09/17/10064318.aspx

How did that guy even think of this simple fix, I wonder?

Hope it helps you…

Just wanted to write about a baffling problem I came across while debugging my web service in Visual Studio 2008.
I was running in debug mode and when I called a method that I had set up breakpoints in, I kept getting an error stating “There is no source code available at this location”.

As always, one should take a step back and try to understand the issue.
The message seemed to indicate that the assembly debug symbols/information and code were out of sync. To verify that, I made a change to the names to one of my web service methods and sure enough, the (auto-generated) debug page for an asmx still showed the old method name. Clearly, my code was not being built.
I fixed the problem by checking the Build checkbox (which somehow got unchecked) in the Solution – Properties – Configuration VS dialog.
As a side, always ensure that your assemblies are built the way you assume they are. Maybe, even delete the dll files to be sure and then do a build/debug and ensure that, if you’re using Internet Explorer to debug), the “Show friendly errors” and “Disable debugging” is off.