"The web server process that was being debugged has been terminated by Internet Information Services(IIS).  This can be avoided by configuring Application Pool ping settings in IIS."

  Very easy fix by following these instructions....

1. Open the Administrative Tools window.

2. Click Start and then choose Control Panel.

3. In Control Panel, choose Switch to Classic View, if necessary, and then double-click Administrative Tools.

4. In the Administrative Tools window, double-click Internet Information Services (IIS) Manager.

5. In the Internet Information Services (IIS) Manager window, expand the <computer name> node.

6. Under the <computer name> node, right-click Application Pools.

7. In the Application Pools list, right-click the name of the pool your application runs in, and then click Advanced Settings.

8. In the Advanced Settings dialog box, locate the Process Model section and chose one of the following actions:

   1. Set Ping Enabled to False.

      —or—

   2. Set Ping Maximum Response Time to a value greater than 90 seconds.

   Setting Ping Enabled to False stops IIS from checking whether the worker process is still running and keeps the worker process alive until you stop your debugged process. Setting Ping Maximum Response Time to a large value allows IIS to continue monitoring the worker process.

9. Click OK.

10. Under the Services and Applications, click Services.

    A list of services appears in the right-side pane.

11. In the Services list, right-click Terminal Services and then click Properties.

12. In the Terminal Services Properties window, locate the General tab and set Startup type to Manual.

13. Click OK to close the Advanced Settings dialog box.

    Close the Internet Information Services (IIS) Manager window and Administrative Tools window.

MVC is a framework methodology that divides an application's implementation into three component roles: models, views, and controllers.  Interested...check out the following very excellent list of resource that can be found here

Very nice add-in which modifies the vertical scrollbar inside of Studio 2005/2008.  The download is small and can be turned off very easily through the Tools-Add Ins menu.

Download Rocky Downs' RockScroll for Visual Studio

If you are a user that lives in an application day-in/out you must force yourself to learn the shortcut keys (at least until voice recognition becomes efficient).  For developers, simply remove the toolbars which immediately forces you to the shortcuts.

Very quickly you will notice clear clutter free IDE.

If you need assistance use the following to help out Visual Studio 2005 Keyboard Shortcut Posters

I often need to open Windows Explorer and browse to the current file, folder, or project that I am working on in Visual Studio. This tip allows you to achieve this by clicking "Windows Explorer" in the Tools menu, and is one of the most simple-yet-useful tips I know of.

To set it up, click Tools, then External Tools..., then click Add.  Now enter the following data:
Title: Windows Explorer
Command: explorer.exe
Arguments: /select,"$(ItemPath)"

Leave Initial directoy blank, and click OK.  Now when you click Tools, Windows Explorer, Windows Explorer will open with the current file you are editing selected.

Adding Windows Explorer to the toolbar

Right click on toolbar and select customize.   Select 'Tools' and if you have not added other External tools then select "External Command 2".  After you drag External Command 2 to the standard toolbar it will change to Windows Explorer.





I have also set the Alt-E key to open Windows Explorer also by selecting "Keyboard" and finding Tools.ExternalCommand2 and setting Alt-E as the shortcut.

If you set a label to a form element set the AssociatedControlID property. This will force the label to render as <label> rather than <span>. A benefit of using the AssociatedControlID property is that clicking a label when this property is set automatically changes the form focus to the associated form input.

When saving files from within Studio I was prompted  to "Save As", "Overwrite", or "Cancel".  I thought it was very odd.  I then looked around and noticed that none of my files displayed the typical source control lock.  It looked like my solution was not connected or related to source control.

For some reason I had lost my connection to Team Foundation (Source Control).  Confused for a little... I then noticed that VS.NET 2008 had this "Go Online" option. 

Nice...offline support for source control is now built into Studio 2008.  In 2005 there was an add-on tool to review and reconnect disconnected files to source control.

After selecting "Go Online" Studio 2008 will check the solution for changes while you were offline and will show a dialog window with the differences.  Now, when checking in you will see those files that you modified while offline as files that need to be checked in.