Thanks to Martin Hinshelwood, a Team System MVP, for sharing the following workaround with all of us!

Excerpt below copied from solution-to-connecting-to-tfs-using-https-over-the-internet.aspx

This problem it seams is to do with the way Visual Studio 2010 connects to your TFS server over HTTPS. The default value for “BypassProxyOnLocal” in Visual Studio 2008 was “False”, but it has been changed to “True” for Visual Studio 2010 Beta 1. It should be noted that this is currently a Beta 1 workaround and this behaviour may be updated for Beta 2 and RTM.

You can fix this by adding the following registry keys and restarting Visual Studio 2010:

You need to add a “RequestSettings” key to both of the following location that contains a string value pair of “BypassProxyOnLocal=’False’”.

32bit OS Key Locations:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TeamFoundationServer

\10.0\RequestSettings

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio

\10.0\TeamFoundation\RequestSettings

64bit key locations:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\TeamFoundationServer

\10.0\RequestSettings

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio

\10.0\TeamFoundation\RequestSettings

You can find out more on the “How to: Change the BypassProxyOnLocal Configuration” documentation on MSDN.

Technorati Tags: CodePlex Tips

Whenever you create or edit a public release (show to public = yes), there’s the Default Release option.

Having a default release will change a project’s homepage from this

to this

Technorati Tags: CodePlex Tips

Yesterday’s tip discussed how to create a planned release. Today’s tip talks about how to assign work items to a planned release so that you can let your users know what you’re planning.

A planned release is treated the same way as any other release, so it will appear in the Issue Tracker just like any other release.

Technorati Tags: CodePlex Tips

When I first got started in the OSS world, I learned that one of the best ways to encourage contributions is to plan releases based on when feature work is done. For example, if you say, “I plan to release version 2 on such and such date” users will sit back and wait for that date to download the release (well, that’s what I would do!) But, if you say, “I plan to release version 2 when features x, y, and z are done,” there’s a better chance of getting community collaboration on the project.

On CodePlex, you can create a Planned release to indicate your intensions of what you want to go out into a future release.

To do this, you’ll need to create a new release and mark the Development Status as Planning.

Now your release will appear in the Planning section.

Technorati Tags: CodePlex Tips

You can create a hidden release in case you need to archive older releases. Only project members can view hidden releases.

To do this, while you are editing a release, you’ll find the Show to public option. Selecting no will put the release under the Hidden section.

Technorati Tags: CodePlex Tips

Okay, you can’t really customize the work item template. But, CodePlex Work Items have a custom field that allows you to insert any text you want into the custom field.

For example, you could use this custom field as a Priority field, in case you’re using the Impact field for Severity. (Priority = when; Severity = how bad). Or you could use it to tag work items as a certain kind, like “UIbug” that i have above.

Then you can search against this custom field.

Technorati Tags: CodePlex Tips

sorry for the delay in the tips. Preparing for TechEd took a lot out of me. And the fact that it was sunny the past few weekends in Seattle didn’t encourage me to stay indoors.

Prior to the April 9, 2009 deployment, the only way for users to find out about updates to work items was through RSS. I’m one of those people who will give up email when you pry it from my hands.

If you are like me, you can now go to any work item and check the “Email me when…” checkbox at the bottom.

Mail notifications to track work item updates is our #3 most requested feature, but I haven’t closed it yet. Having individual work item notifications is just half of the fix, as this is really for visitors to the project. The other half of the fix is for project owners to receive a daily digest of newly-entered issues. When that is deployed, I’ll close this work item.

Technorati Tags: CodePlex Tips