Error: The build must be stopped before the solution can be closed.
Description: When attempt to close Visual Studio solution or project while the build is running the exception windows throws up.
Solution: First stop the build or kill the process devenv.exe (if the solution got crashed) and then close the solution.
Error: A Command with that name already exists.
Description: This error usually pops up from Visual Studio when there is a corrupted add-in or extension added into VSPackages.
Solution: Identify, remove and reinstall the extension. And run the following command Devenv.exe /ResetSkipPkgs from Visual Studio Command Prompt. /ResetSkipPkgs clears all options to skip loading added to VSPackages by users wishing to avoid loading problem VSPackages, then starts Visual Studio.
Edit: How to remove Addins from Visual Studio.
Open path – C:\Users\username\Documents\Visual Studio 2010\Addins and remove the necessary files.
Then type and run devenv /resetaddin following command from Visual Studio Command Prompt.
Error: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Description: There can be many reason.
- The request to SQL Server or query is taking a long time to execute.
- The result is returning large amount of records.
- Slow network connection issue.
- SQL Command connection timeout is not configured properly.
- Badly made SQL statements
- Check the network connectivity is up and running.
- Check the SQL Statements, if required tuned and optimize it.
- Check the result size.
- Configure Connection Timeout property, by default it’s 15 seconds.
Error: The Web Application Project ” is configured to use IIS. To access local IIS Web sites, you must run Visual Studio in the context of an administrator account.
Description: While trying to run the Visual Studio 2012, 2010, 2008 etc, we might get this error. Why we getting this error, the reason is there in Error itself. Because of the security model configured for IIS7 (am using). IIS7 configuration derives from NTFS ACLs on the distributed .config configuration files as well as Allow/Deny/Inherit logic of the configuration properties within the distributed .config hierarchy. So in order to run all the features, IIS requires administrative privileges. So if Visual Studio needs to access the web site hosted or pointed over IIS requires an administrator rights.
Solution: Multiple ways are there…
1. Right Click on VS, and Run as administrator.
2. Those who don’t want to access local IIS Web sites then edit the project, under node ProjectExtensions, VisualStudio, FlavorProperties, WebProjectProperties find node <UseIIS> and change the value to False. Reload the project.
3. Or, add more privileges to your logged in account from UAC.
More Read: MSDN Blog, Technet
Error: Unable to start debugging on the web server. See help for common configurations errors.Running the web page outside of the debugger may provide further information.
Description: This error occurs while running or debugging an application using Visual Studio 2010. The reason behind this problem is because of .NET framework version configured for your project and the IIS Default App Pool or the Pool that configured for your application is not matching correctly. For example: .NET framework configured for project is v3.5 but at application pool level it might be v4 or higher. At this time VS was unable to find out which pool should pick for debugging.
Solution: Go to Application Pool using, click Basic Settings under Edit Application Pool and remap the correct .NET Framework version.
Example: If project using v3.5 then remap .NET Framework version to v2.0, rerun the project again.