If you are annoyed at the IIS timeouts when running .NET code via Visual Studio then you'll want you know how to fix that problem!

You can do 1 of 2 things.
* Go to the Application Pool for the Web Application you are working with. Select the Advanced Settings. Set the Ping Enabled property to False. This will allow you debugging to run forever.
* If you prefer to allow IIS to continue the monitoring process then change the Ping Maximum Response Timeout value to something larger than 90 seconds (default value).

It is a pain to set the default browser in Visual Studio UNLESS you use a brilliant tool like this.

WoVS Default Browser Switcher
http://visualstudiogallery.msdn.microsoft.com/bb424812-f742-41ef-974a-cdac607df921/

Have you ever wanted to clear the list of Projects from the Start Page in Visual Studio? Here's how to do it.

Run --> RegEdit  and navigate to: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\<your version>\ProjectMRUList.

Delete the entries that you don't want.

You can also remove the recent list of files by clearing entries in the HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\<your version>\FileMRUList!

One more thing to mention. If you get those annoying Project names like Project (2), Project (3) and just want to start over then you can do that be deleting the folders in My Documents\Visual Studio 2008\Projects\. Usually these folders will only contain the Soluntion (*.sln) files.

Happy Programming!
Dave

Today I ran into more issue when working with deployment of my very first Web Part using Visual Studio 2008 on a 64bit Windows 2008 OS. One important tip when trying to deploy using a SharePoint WebPart for within Visual Studio as that you MUST add the VSeWSS user to the Sit Collections Administrators list. By default that will be just the Primary and Secondary admins of the Site Collection.

Note that you will probably only run into this issue if you have installed Visual Studio 2008 extensions for Windows SharePoint Services 3.0, v1.3 WITHOUT first creating the VSeWSS Application Pool. Please refer to the Release Notes as it will explain how to add the VSeWSS local user to all the required groups.

CAUTION: if you come across a post on the web that tells you to run this comment, then be VERY CAREFULL as it will knock-out your 64bit WSS SharePoint Web Applications if that's what you have: cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1. Only Enable 32-bit on the VSeWSS App Pool.

Hope you have as much fun as I did, but it is great when I was finally able to deploy from within Visual Studio.