Why is Debugging in VS slow and takes forever saying "Loading Symbols..."

I encountered an issue in one of my Win 2K8 server machine where debugging a simple application in Visual Studio was taking forever. Everything was fine if you run the application but as soon as you tried debugging it, the performance was really slow and it took forever saying "Loading Symbols..."

When I went to Tool->Options->Debugging->Symbols, I found that it was referring to an environment variable _NT_SYMBOL_PATH whose value was some url which wasn't reachable.

I deleted this environment variable from My Computer->Properties->Advanced System Settings->Advanced->Environment Variables... and everything was fine after that. I was able to debug the application without any issues.

TFS 2010 - Associate existing test cases with test methods

If you want to create new test cases which are associated with test methods, tcm.exe will solve your purpose.
However, what if you want to associate existing test cases with test methods.
Here is the thread on MSDN forum which poinst out how to associate existing test cases with test methods http://social.msdn.microsoft.com/Forums/en-US/vsmantest/thread/774642af-fa44-473d-ab6d-817cfa83cf10/

TFS 2010 API - Create WorkItems(Bugs)

Here is my TechNet article
http://social.technet.microsoft.com/wiki/contents/articles/3280.aspx

TFS 2010 API - Get Results of a Test Run

Here is my TechNet article
http://social.technet.microsoft.com/wiki/contents/articles/3279.aspx

VS 2010 - No more Private Accessors (Publicize) and Code Generation

According to the below article, the visual studio team has stopped working on Private Accessors (Publicize) and Code Generation features from VS 2010
http://blogs.msdn.com/b/vstsqualitytools/archive/2010/01/18/publicize-and-code-generation-for-visual-studio-2010.aspx

There are other alternatives which are listed in this article.

VS 2010 - Different Timeouts in Testsettings file

The following are the different types of timeouts that can be configured in testsettings file:

• agentNotRespondingTimeout
• deploymentTimeout
• runTimeout
• scriptTimeout
• testTimeout

Setting these timeouts are not very obvious when the testsetting is opened with 'Test Settings Editor'. Hence, open the testsettings file in 'XML (text) Editor'

You can then add various timeouts in milliseconds in the Timeouts node under the Execution node.
<TestSettings name="Local" id="46d8e12e-16c0-4ba4-9dd9-eda66fb2ccc6" xmlns="http://microsoft.com/schemas/VisualStudio/TeamTest/2010">
   <Description>These are default test settings for a local test run.</Description>
   <Execution>
     <Timeouts agentNotRespondingTimeout="1800000" deploymentTimeout="" runTimeout="1800000" scriptTimeout="1800000" testTimeout="1800000"/>

VS 2010 - Create Load Test Repository

One day I found that my Load Test Reporsitory is missing and hence I was not able to run the load tests.
The load tests were failing with the error:
---------------------------
Microsoft Visual Studio
---------------------------
Error occurred running test. The load test results database could not be opened.  Check that the load test results database specified by the connect string for your test controller (or local machine) specifies a database that contains the load test schema and that is currently available.  For more information, see the Visual Studio help topic 'About the Load Test Results Store'.   The connection error was: An error occurred while attempting to create the load test results repository schema: Cannot find the object 'LoadTestTestCaseSummary', because it does not exist or you do not have permission.
---------------------------
OK  
---------------------------
To resolve this issue, I followed the below steps:
1) Open VS command prompt in elevated mode (Run As Administrator)
2) Run the command "cd C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE"
3) Run the command "SQLCMD /S localhost\sqlexpress /i loadtestresultsrepository.sql "