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
Related
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.
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.
Everytime I try to run my code, I am having this error that "Csc.exe" exited with code -1073741819
, I cleaned my solution and restarted Visual Studio with no gain.
Can anyone help me?
I faced same problem. Delete the bin and obj folder in project(s). The try to clean and rebuild the solution. This worked for me.
Cleaning and rebuilding the solution will sometimes solve the issue and sometimes won't.
You need to repair Visual Studio. Go to Control Panel -> Programs. Then select your version of Visual Studio you are using and press "Change"(or right click it and press "Change"). When the setup appears, click "Repair".
This solved it for me and several others who have been facing this issue.
For the problem csc-exe-exited-with-code-1073741819
I repaired Visual C++ 2015 Redistributable (x86). This worked for me.repair Visual C++ 2015 Redistributable. I found about this problem when uninstalling and then reinstalling VS2015. After the setup is completed it says that some items are not installed correctly. And among them is Visual C++ Redistributable for Visual Studio 2015 not installed correctly.
So after a while I repaired Visual C++ Redistributable 2015. Here is the link Visual C++ Redistributable for Visual Studio 2015.
classic ms solution: restart computer :D
delete bin and obj folders
open vs
build
it should work.
I want to share my experience here because I had this problem for several days (with VS Studio 2012) and I had MANY MANY difficulties to find the solution !
And my problem was... That I had a virus/malware problem, and the faulty module was BITGUARD !
So if someone has this problem, and goes here searching the solution, I think you must try any free Malware remover program to see if Bitguard should not be your problem !
Regards,
Olivier.
I also had this problem, and luckily found a solution.
First off is more of a workaround, but seemed to work. Disable parallel build in Visual Studio
(Tools -> Options ->Projects and Solutions -> Build and Run. Change maximum number of parallel builds to 1).
This resolved the issue for me, but did not solve the problem.
The issue I had, as obscure as it is, was I had Razer Synapse set up to record mouse and keyboard stats on Visual Studio. Once I disabled this, everything worked perfectly.
When our company changed anti-virus software, an application that had not been touched in months suddenly started having the build error
"csc.exe" exited with code -532462766..
I used our new AV client to scan the bin folder of the application that wouldn't build. The AV client claimed it was infected with W32.Trojan.Genkd. Uninstalling that AV software allowed it to build as usual. I think a single file got quarantined, preventing the build.
Your options may be these:
disinfect the files (assuming it's an actual infection)
unquarantine the "infected" files (assuming it's actually safe)
uninstall / disable that AV client
change AV software
Lastly, you could always comment blocks of code to identify what is causing the false-positive.
I got this error when running from the devenv command. Adding /SafeMode to the command arguments solved my issue which lead me to think one of my install extension/plugins for VS2015 was to blame.
I Resolved the same issue by Restarting my PC and that's it.
My Visual Studio began crashing at start-up. In my search for finding a remedy, I found these two suggestions, but neither worked for me:
Launching Visual Studio while running in safe mode, and
Running repair on Visual Studio.
However, I found that if I logged into a different Windows account, Visual Studio was able to run from that account without crashing.
Here is an error code that that I observed in the crash report:
LCID: 1033
Can anyone provide a solution for returning my Visual Studio to working order?
For me it turned out to be the plugin that GitExtensions installed into Visual Studio 2013.
-- UPDATE: try this before uninstalling GitExtensions
#Enceradeira proposed in the comments to uncheck the Show current branch in Visual Studio option. In GitExtensions, you get there via Tools -> Settings -> Appearance:
-- END OF UPDATE
After uninstalling GitExtensions and reinstalling it with all VS plugin unselected my VS runs smoothly again.
I even put together a blog post about this issue because it bugged me so much.
Since you're able to run with another user login, something may be wrong with your local settings, you can try to reset them: devenv /resetsettings in Start menu -> Run.
Warning: this will restore visual studio to default settings.
In my case VS used to crash on a single solution. I resolved the problem by deleting the respective solutions's user file: SolutionName.suo
My colleague recently experienced a problem with Visual Studio 2013 crashing on start-up. Unfortunately, we found that the approach recommended in the answer by #Arun M did not solve the problem:
devenv.exe /ResetSettings
...however, using a different command line argument did:
devenv.exe /ResetUserData
An easy way to run devenv.exe is via the Visual Studio command prompt; on Windows 10, it can be found here:
Start Button => All Apps => Visual Studio 2013 => Visual Studio Tools =>
VS2013 x86 Native Tools Command Prompt
For more about these command line arguments for devenv.exe, see this answer to this related question: How do I truly reset every setting in Visual Studio 2012?. ⚠ In particular, please note the cautionary statement in that answer about the /ResetUserData command line argument!
Try to run VS as administrator. That's necessary in my case.
If coincident to these Visual Studio crashes you are getting "Heap corruption" (Exception code: 0xc0000005) errors in your Windows Application log (Faulting module name: WindowsCodecs.dll), here is something worth checking into: A faulty WIC component within Expression Blend can cause ALL versions of Visual Studio to crash upon launch, as well as cause Internet Explorer to crash upon visiting many, if not most sites. Even though Microsoft distributes this component, they call it a "non-Microsoft component". As such, a Visual Studio reinstall won't fix this,, an OS reinstall over existing Windows installation won't fix this, and a system file integrity check won't detect it.
If my case, the misbehaving codec was "C:\Program Files (x86)\Microsoft Expression\Common\Imaging\4.0.360.0\PSDCodec.dll", and simply unregistering this component got my Visual Studio working again from consistent startup launch crashes.
I post this in hopes this solution to one source of Visual Studio crashing might save others from the $500 Microsoft support incident fee and week of downtime this caused me.
I just changed the windows language in the bottom right to "EN", then started as admin. And it worked, interesting..
I had the very strange phenomenon that both Visual Studio 2010 and 2013 on a Windows 7 machine crashed when run in a remote desktop session, started from a Windows 10 pc. Debugging the crash showed a CultureNotFound exception. It was caused by regional settings on the Windows 10 pc, which could not be translated in something understood by Windows 7. I had language English(Belgium) with an Azerty keyboard. I added and selected English(UK) with an Azerty keyboard and the crashes disappeared. No other programs suffered from this.
For me it was being caused by Web Essentials and I was able to resolve by disabling it, restarting VS, enabling it back , restart again. Works now.
I had a crash on startup (or soon after startup, before opening any solution) occurring in git2-msvstfs.dll, caused by placing a 3GB temp file into a directory within my solution. Deleting the file fixed it.
Once I accidentally pressed a random key combination (maybe something like ctrl+', but I didn’t realize I was holding ctrl down so I forgot what keys I hit by the time I realized something bad had happened) that resulted in VS Professional 2017 15.3.5 crashing within half a minute. After relaunching, I found that VS would be interactive for a few seconds before it would crash within half a minute. It was really too fast for me to try to figure out what I had accidentally activated or for me to disable it before VS would crash. Also, it would even crash if I didn’t open any solution, so I figured it was not something that deleting a .vs (per project/solution Solution Explorer/open files state) folder would fix.
To fix, I followed Arun M’s comment and renamed my %LOCALAPPDATA%\Microsoft\VisualStudio\15.0_3f4d04be folder. You will need to adjust the path for the edition/version of VS that is crashing. On my machine, I think 15.0_3f4d04be is Professional and 15.0_0fed6c59 is VS Community Edition. You’ll probably have to guess based on the folder’s modification timestamp which is probably going to reflect the date you last used that edition of VS.
After renaming the versioned dotfolder, VS launched without crashing. It started with default settings but automatically restored some of my settings through the cloud sync stuff after a minute of running and it even remembered my account information so I didn’t need to sign in.
I did not need to rename my %LOCALAPPDATA%\Microsoft\VSCommon folder (which Arun M had also suggested).
I had a similar problem, both VS2015 and VS2013 would crash at startup. Tracked it down to an application I installed which put .net 4.7.2 on the system. Once i removed that app, removed .net, and reinstalled .net 4.6, Visual Studio started working again.
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!