I attempted to launch a website project locally but received the below message in an error dialog:
Please correct before proceeding.(You might rename the current web.config and add a new one).
Typically this error is preceded by a general description of the cause, this one was not. Knowing odd, out-of-the-blue, problems such as these are typically related to corrupt IDE generated files. I tried deleting the .suo, .vssscc and other generated files from the solution and project directories but the problem continued.
This happened to me today after getting latest. I resolved by closing and reopening the solution, rebuild, then run. All is well...
I actually resolved this by making sure the Web.config file wasn't an open document inside VS 2015. In other words, close the Web.config file wherever it might be open, and make sure your Team Explorer isn't causing any problems, like an unexpected change or staged change...rebuild the sln and run...
Close vs2017 and open it again worked for me
just open web.config and run again.I've had this problem and I resolved by this solution .
I fixed the problem using a solution I found for a different IDE-related issue (original answer here). Run the following in an elevated command prompt:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe" /setup
Note: You'll need to adjust the path for your version of Visual Studio (original version mapping answer here):
Visual Studio 2005 = 8
Visual Studio 2008 = 9.0
Visual Studio 2010 = 10.0
Visual Studio 2012 = 11.0
Visual Studio 2013 = 12.0
Visual Studio 2015 = 14.0
This issue came to me after merging some code in version control using RTC tools. When I saw whyoz answer I noticed that web.config wasn't opened anywhere. It could be RTC locking the file or something like this. So, I simply restarted Visual Studio and it became normal again.
I ran into this issue today after doing a branch merge using the VS19 built-in Git tools. The config file was correct; I even used a schema validator based on KD2ND's answer in how can I validate dot net application config file(ex, app.exe.config) on console?.
I cleaned the solution, unloaded it, and reloaded it, and everything worked fine. I didn't even need to restart studio.
Based on others' answers, this appears to be related to code merging in the IDE. It's a weird problem but it's a relief that the solution (once found) is simple.
As an FYI, in VS 2019 the solution is to close the tabs, and the solution and Visual Studio, then restart Visual Studio. This has worked for me.
in Microsoft Visual Studio 2019 : Just neeed to close project, thenn open+ clean+rebuild and everything work
In VS 19 Enterprise, the Solution for me was:
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\devenv.exe" /setup
Based on the merked answer from alan.
I had just opened the web.config file and then pressed CTRL K + D. it will make the formatting good of the file. and then run the application. it worked for me.
Even if you undo the above changes then also it works. it is weird somehow.
Related
First of all, I am trying to open a support request with Microsoft about this issue, but their support reporting portal isn't working. I have resorted to Stackoverflow because I have no way of getting to Microsoft.
Yesterday, I started updating Visual Studio 2022 from Visual Studio Installer by mistake and paused it shortly after. Today, I tried to open a project but Visual Studio seemed unavailable. At that point I remembered about the paused update and re-opened the Visual Studio installer. I tried to Resume, and I got the below error. The Modify and Remove options give out the same error too. There is no Repair option.
Sorry something went wrong
The dependent package of
'Microsoft.VisualStudio.Debugger.Concord,version=17.1.33203.90,productarch=x64'
cannot be found: Microsoft.VisualStudio.DebuggerClient.Concord,
version=[17.0,18.0].
I also tried Restarting and deleting temporary files using the Disk Cleanup tool - no difference.
I have tried to force an uninstall from the Add or Remove programs but this still redirects me to the Visual Studio installer.
I have tried to research this error online but found nothing.
I did not fix the issue but at least I managed to uninstall the Visual Studio instance to be able to start from scratch again. If you do not want to go down the route of uninstalling, feel free to try the steps as suggested by #garbagecollector.
I deleted the installation folder for 2022 from ProgramFiles.
I deleted the Visual Studio installer from Add or Remove programs. (Note: This actually uninstalled a working version of Visual Studio 2019 that I had, and left the messed up version of 2022 with the same issues, so beware if you do not want to uninstall another working version of Visual Studio)
Then I ran InstallCleanup.exe via CMD (in admin mode). Refer to the "Remove All with InstallCleanup.exe" section within this article. This seems to have cleared all Visual Studio related files including the Visual Studio
installer, and I could re-download the installer for Visual Studio
2022 Community edition and start afresh.
I faced the same issue today and could solve it by removing corresponding dependencies from _package.json files from C:\ProgramData\Microsoft\VisualStudio\Packages\[PACKAGE_NAME] folders.
I am not sure whether you can repair your installation this way, I tried only with uninstall.
So in your case edit this file:
C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualStudio.Debugger.Concord,version=17.1.33203.90,productarch=x64 and remove the line marked with "-->" under "dependencies":
{
"id": "Microsoft.VisualStudio.Debugger.Concord",
...
"dependencies": {
...
--> "Microsoft.VisualStudio.DebuggerClient.Concord": "[17.0,18.0]"
}
}
In my case I had to repeat this procedure for three or four _package.json files.
We are running into a problem opening our MVC5 solution in Visual Studio 2017. It will show a message saying loading projects, followed by "Preparing solution" and then it just freezes. Some preliminary research has lead to suggestions like
Remove the hidden .vs folder
Repair installation by running as admin
Updating to the latest released VS build
Remove any node.js type folders that have deeply nested folder structure within the solution folder
However, none of these have worked. Has anyone else run into a similar problem using VS 2017 with their solution? There are no special commands on packages loaded on startup.
I was able to finally get it to work. I updated to the latest Visual Studio build 15.0.0+26228.10, but that did not seem to help. After removing my .vs folder before opening the solution multiple times, it finally started to load. I have no 3rd party extensions or tools running.
I installed visual studio enterprise 2017 version 15.0.0+26228.10. and productivity power tool extension. the studio keep crashing when load project. I uninstall everything and reinstall vs only, the crash problem disappeared.
Deleted the vs folder, but it didn't work.
Looked for recently changed files in the project, saw Web.csproj.user — when I removed this the project works again.
Visual studio 2017 keeps crashing when i try to launch it,all i did was to launch visual studio installer go to more which is under the product am using then clicked on repair and that got me running again.
We saw some lockups, especially during the start of Batch Builds, until we set this experimental feature to False:
Tools > Options : Text Editor > C/C++ > Experimental : Enable Faster Project Load.
I don't know whether it could apply to your problem or not, but it is related to loading projects, so...
Good luck.
I had the same issue and uninstalled the ankhsvn subversion plugin then closed and re opened vs 2017 ad it worked.
I'm running Visual Studio 2012 (version 11.0.61030.00 update 4). When debugging a local console application I get the following error when I start debugging (F5):
---------------------------
Microsoft Visual Studio
---------------------------
Error while trying to run project: Unable to start debugging.
The object invoked has disconnected from its clients.
---------------------------
OK
---------------------------
This only happens if I leave visual studio alone without debugging for a couple minutes. If I close visual studio and re-open the error goes away (until I leave it untouched for another couple of minutes). Has anyone experienced this? I can't find any threads of other people experiencing it.
This may be a possible answer for the problem.
Some from the answer:
Check which files were changed (why and how) after update from a source control engine
Review the list of extensions and plugins. Try to disable all or some of them
Close Visual Studio and kill all the development processes: devenv, mspdbsrv, vcpkgsrv, msbuild, msvsmon, vshub, vstest etc
Remove .suo, .ncb, .VC.db, .VC.VC.opendb files of the solution as well as .vs directory, which sometimes cause problems
Remove project setting files, sort of YourProjectName.vcproj.DOMAINNAME.LOGINNAME.user or YourProjectName.csproj.user. The setting file name depends on a project kind you use
Run "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" /setup or "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" /setup for x64 environment
Just Close the VIsual Studio and start again the project.Its work Perfectly for me.
Thanks
While restarting Visual Studio does provide a workaround, it doesn't solve the actual problem. In my case, I was working with a C# solution in VS2017 and the following resolved the issue:
Close Visual Studio
Delete the .vs folder that was created in the Solution's directory
Re-open the Solution
I corrupted my App.config file with NLog settings without section Handler in the top of the document. Gist is check out your config file settings either corrupted in format or not properly handled any section. once I remove corrupted config section, it did not raise the error again (VS 2017)
Hope it helps!
In my case I have just reinstalled Windows 10 and so the Visual Studio 2022..
My project was targeting .net 5 SDK, but I only had .net 6 SDK installed. The solution was to install earlier version of the SDK.
I just installed VS 2010 v 10.0.30319.1 RTMRel on 64bit Win7 Ultimate and keep receiving the following error when I try to open a web project. I have repaired and reinstall but the issue persists. I am looking for resolution suggestions. Thanks
The 'Microsoft.Data.Entity.Design.BootstrapPackage.BootstrapPackage, Microsoft.Data.Design.BootstrapPackager, Version 10.0.0.0.... did not load correctly.
This was happening to me as well. In my case I installed Visual Studio on my D drive which is not my system drive. After reading a link found in ChiliYago's blog post I found that the root cause was that files were missing from %ProgramFiles%\Microsoft Visual Studio 10.0\Common7\IDE (Which is what the error message says).
In my case, the missing files were installed in C:\ProgramFiles (x86)\Microsoft Visual Studio 10.0\Common7\IDE and not D:\ProgramFiles (x86)\Microsoft Visual Studio 10.0\Common7\IDE. My solution was to copy the missing .dlls from the install directory on the C drive to the install directory on the D drive, and the error stopped happening.
I had previously installed an Express edition of C# and un-installed it before adding Visual Studio 2010, this may have contributed to the problem for me.
In my case, I Installed Entity Framework June 2011 and then uninstalled it. After this I had this problem.
Nothing found in internet worked and when I was going to format I found in the directory: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\CommonExtensions\ these 2 files:
Microsoft.Data.Entity.Design.BootstrapPackage.pkgdef
Microsoft.Data.Entity.Design.Package.pkgdef
Here is when VS 2010 is trying to load the library that cannot load.
I have another PC with Entity Framework 4.0, and it doesnt have these files, so I have moved them out to the desktop. Now Visual Studio is loading the project succesfully.
On the other hand, my problem also was that If I choose to hide the error message then Entity Framework 4.0 didn't create the .Designer.cs of the Model. then when I tried to add the Domain Service Class to the project, the context class didnt appear (but yes in another machine with the same project and same database).
Now that I have not the error message everything looks working good.
I hope it helps others because I have had this problem during weeks.
Best Regards,
Tried the uninstall and reinstall of Visual Studio 2010… Still that had the damn annoying message about the Missing Assembly.
Looked on the C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\ Directory which only showed:
Microsoft.Data.Entity.Design.DLL
Installed a LOT of Windows Server 2008 files (32 Bit OS) in regards to SQL Server 2008… ADO.Net, etc… STILL didn’t solve the issue! GRRRRRRR!
So I finally fixed the issue by reading between the lines. See the details below on how I resolved this issue…
This points to the MISSING Assembly:
Microsoft.Data.Entity.Design.BootstrapPackage, Version=10.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/VisualStudio/10.0/Packages/{7A4E8D96-5D5B-4415-9FAB-D6DCC56F47FB}
Renamed Key to:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/VisualStudio/10.0/Packages/{7A4E8D96-5D5B-4415-9FAB-D6DCC56F47FB}-123
Problem Solved for now in Visual Studio 2010!
Hope this helps someone else resolve this issue!
I've managed to completely remove VS 2010 from my computer using official utility and then reinstall it. Problem disapeared.
From tools menu in VS2010 select Import and Export Settings...
Select the last option, reset settings.
Save them, why not :)
Select a canned default, such as Visual C#.
Post your differences here, so that you know what to re-enable, and Microsoft people know what needs to be fixed.
I've had same problem, i solved it by rapairing it from "Control Panlel" clicking "Change/Remove" and tan choosing "Repair". BTW i'm using Win XP but i think that uninstallers in Visual Studio are the same. So.. Good luck!
A while ago I noticed I don't have a magnifying-glass next to my datatables. I used to have it, and somehow, sometime, it disappeared...
Has anyone seen this happen? Do you know how to help me view my datatables again?
Update: I'm still clueless about this. Could anyone point me in some direction, where should I even start looking for an answer? Thanks a lot.
Update: I changed to a new computer, and still the same problem. But I pinpointed it to being only in Visual Studio 2005. On Visual Studio 2008 I have perfectly normal DataSet and Datatable visualizers.
So I tried re-installing VS2005, to make sure all the components were installed, nothing left out - but Nada. Still no visualizer.
Update: Found the solution to my problem: My answer
I was really bothered by the problem, so I turned to Microsoft support, and they solved my problem! The short solution is that apparently one of the DLL's in the My Documents\Visual Studio 2005\Visualizers folder was corrupted. I deleted all the contents of the folder, and the visualizer came back.
The long answer can be found in this post written by Faruk Celik - the person from Microsoft who solved my problem.
Create a new clean project, does the Visualizer show up there?
Check if this file exist: "\Program Files\Microsoft Visual Studio 8.0\Common7\Packages\Debugger\Visualizers\Microsoft.VisualStudio.Debugger.DataSetVisualizer.dll"
Check if the dll is loaded in Visual Studio, Open your project, then open anther Visual Studio, attach the debugger into the first Visual Studio (Make sure that managed debugger is selected). Inside the debugging Visual Studio open Debug/Windows/Modules to see if the DataSetVisualizer is loaded.
try devenv /ResetSettings from an admin console.
I know this is an old post, but I have been fighting this same issue. Nothing solved my problem... I finally figured out that I had been running Visual Studio in compatibility mode (Windows 7 os). Once I ran devenv.exe without compatibility mode set, the visualizers showed up again.
Give devenv /resetskippkgs a try...
I am using Visual Studio 2017 and I had the same issue. I realised the visualizers folder is missing in my documents. I think this is something to do with the recent windows upgrade on the office computer. I have resolved it by creating an empty Visualizers folder.
I have the same problem and it drives me crazy. Finally, I have it works after trying many advice from Googling and trail and error.
\Common7\IDE\devenv.exe /resetuserdata at the command prompt.
I rename Microsoft.VisualStudio.Debugger.DataSetVisualizer.dll to Microsoft.VisualStudio.Debugger.DataSetVisualizer.dll.test on both
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PublicAssemblies
And
\My Documents\Visual Studio 2005\Visualizers
I was having the same problem, nothing would appear when I hovered over my dataset variable. I was finally able to see the dataset visualizer when I added my.forms in front of my dataset variable in the Watch window
Execute Visual Studio as administrator. Right click and execute as administrator and the magnifying-glass appears next to datatables.
I tried everything in this post but nothing worked for me. I am running Windows 7 64-bit. Eventually I was able to find a solution in this post
I tried everything here but the only thing that worked for me was to overlay 2 folder using someone else VS 2019 that had the visualizers working.
C:\Users\XXXXXXXX\Documents\Visual Studio 2019\Visualizers --< XXXXXXXX = the user folder
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\Packages\Debugger\Visualizers