I'm getting the following error message
Cannot access a disposed object. Object name: 'MarshalingWindowFrame'.
This message came when I tried to load a SLN file into VS2013.
What is the reason?
I am using VS2013 Ultimate with Update 4 on Windows8.1 pro x64 bit OS (8GB RAM, 500GB HDD)
If you get that when opening a solution, either an addon is bugging out or (worse, but less likely) you found a bug in VS itself. Try safe mode and see if that helps.
If however you get the error when opening a form rather than the solution itself (remember opening a solution loads the various forms), there's a bug in an user control that's trying to access a disposed object. Remember that user controls run as binaries when hosted in VS, so make sure you put actual code inside guards that require you not to be in design mode.
Was that project created in the earlier versions or in the Visual Studio 2013 Preview? Because, if you update this project from Visual Studio 2013 Preview, you have to check the update procedure (http://blogs.msdn.com/b/lightswitch/archive/2013/08/12/upgrading-your-lightswitch-projects-raghuveer-gopalakrishnan.aspx) first, perhaps it can give some hints why this happens.
Related
I have recently installed Microsoft Visual Studio 2015 Community Edition on my laptop.
Since the time of installation I have been facing a few issues.
I was not able to even access the New Project option itself.
Some of the times I will be able to access it however, sometimes it does not even allow me to access a single file of my solution in the startup itself it gives me an error.
I have attached a set of five screenshots in this query. There is some blank space after users path, I removed an extra folder name(username) from the path so dont get confused with that.
The detail of all the screenshots are as follows:
1) This is the image I get when I launch the Visual Studio on my laptop.
2) Once I click 'NO' option on the first dialog box I get a new one stating an error with the source code.
3) Once that is done, I move onto Solution Explorer to access the solution and I get this log.
4) When I try to access the tools tab to check for options I get this error message.
5) I had even tried to create a new project and the following error provided in this screenshot would appear.
I am not able to understand where I could have gone wrong or what happened that has corrupted the application to this extent. Is it an installation issue or are there some bugs in this version of Visual Studio, if there are any I would be more than happy to move to previous versions as I was a lot happier with them than this one.
If someone would help on this concern I would be really thankful.
Regards,
Harrisson
First, I went ahead and uninstalled the current version of Microsoft Visual Studio 2015 from my system. Then, I searched and removed the data from the temporary files related to MS VS 2015 from the following paths:
C:\Users\Username\AppData\Local\Microsoft\VisualStudio
C:\Users\Username\AppData\Roaming\Microsoft\VisualStudio
Once this had been done, I went ahead and installed Visual Studio 2015. After installation, I installed the additional support directories for Visual C++. You can do the same for the platform you wish to work on.
Then I installed updates from the following link:
https://www.visualstudio.com/en-us/news/releasenotes/vs2015-update3-vs
Once I started the solution it worked perfectly fine after that with no errors.
Env: Visual Studio 2015 Community Edition on Windows 8
Trying to open Tools --> Extensions and Updates results in the following error in a message box:
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Tried running as Admin, same result.
I've tried looking at the log but nothing mentions that error.
In the log there are 3 error entries related to extensions which could be related, they say the following:
Error loading extension: Could not find a part of the path 'C:\path\to\APPDATA\LOCAL\MICROSOFT\VISUALSTUDIO\14.0\EXTENSIONS\ZW2UF5JV.JVN\extension.vsixmanifest'.
The other 2 are identical except the odd string at the end is HQ1Y5EQD.TMG and 3KWE1LJF.Z1W.
Interestingly, just before those errors in the log appear, there is a line for each saying the extension was loaded successfully but if I try to go to the path it's got listed, it doesn't exist.
I can't find any reference to those strings on my machine. I've also searched the registry but can't find any reference in there either.
I can get into the Extensions manager if I click on one of the update notifications but the original error message just displays in the main pane and I can't do anything else. I can get to the online window but as soon as I click an extension, I am prompted with the original message.
I haven't installed any extensions or VS updates for a while but my Web Compiler extension extension has stopped auto compiling JSX files which is why I started trying to look at the Extension manager. I'm guessing the issues are related.
I can still work, compiling can be done manually which is inconvenient but not the end of the world. My worry is some other extensions are also misbehaving and I just haven't noticed yet.
Don't really want to re-install VS as a) it took ages last time and b) it might not fix the issue. Is there any good advice on troubleshooting the error or anything else I can try before I re-install?
I refreshed the GitHub extension on VS 2015 and got this error. Deleting the two cache files:
extensions.en-US.cache
extensionSdks.en-US.cache
from the AppData\Local\Microsoft\VisualStudio\14.0\Extensions causes them to be rebuilt and eliminates the error.
No reinstall needed.
Problem got worse, I started getting the error message when starting Visual Studio and things like the package manager wouldn't load. Each restart seemed to yield a different combination of windows not loading, sometimes Solution Explorer, sometimes Team Explorer etc. Not good.
A repair to VS 2015 via the Control Panel took a while but didn't help, same problems.
I ended up completely uninstalling and trying to re-install. However the installer threw an index was out of range error but weirdly VS 2015 was now listed as an installed application again.
So I'm guessing the original uninstall left some problematic files lying around which messed up the next install. So I uninstalled again, renamed Microsoft Visual Studio 14.0 folder, cleared all files from AppData\Local\Microsoft\VisualStudio\14.0\Extensions and re-installed.
It installed and ran fine.
The problem I now had was that I couldn't find the SQL Server Object Explorer window anywhere. I tried repairing SQL Server Data Tools but still no luck. So I uninstalled SSDT and then re-installed. This seemed to fix it.
Now I realised I also couldn't connect to Azure through the Server Explorer window, the option was simply not appearing in the list like it used to. This time a repair to Azure Tools for Microsoft Visual Studio 2015 - v2.9 and a repair to Azure App Service Tools v2.9 - Visual Studio 2015 fixed that problem.
I confronted same issue and found this thread. I tried the above suggestions, but unfortunately, it went all unsuccessful. I even tried to uninstall/install with even worse result as Visual Studio became unable to start due to new "missing components" issue. Reinstallation was nothing better.
I finally came by a piece of magic. It was Visual Studio Uninstaller which although would remove all your installed extensions, it would perform a complete cleanup. It would save you from installing new Windows (at least it was my case.
Just go to releases and download the first zip file
This way you will be able to perform clean install of Visual Studio.
Situation.
I have Web developer Express Studio 2008 installed on my system.
Until recent windows update it worked fine, but about 2 weeks ago it start giving me an error every time I attempt to create any new project. Screen shot of an error below:
Express 2008 error
I did try to do windows restore to point before update and it did not worked.
As a next step I installed Visual Studio 2010(same result) and VS 2015 same result but a bit more descriptive error. Screen show below.
VS 2015 error
But there is no clear information on Microsoft MSDN forums about this error or how to fix it.
I did try to do reset(devenv.exe\resetsettings) but so far no luck.
Any idea what is going on and how to fix this?
Right now I can not create ANY new project and some of older projects are not opening as well. There is no system of or any kind of similarity between projects which opens or not.
This is a fairly vague error as the dll in question isn't listed here and 0x8007045a is just the error code for this dll initialization error. As a next step in troubleshooting to find the issue (outside of a windows repair) I'd go ahead and run Process Monitor and watch the file system activity for Visual Studio (once you see devenv.exe show up, right click on it and include just that process.
There's a blog post with some troubleshooting steps here but really though, you need to find which library is the culprit to track down what you'll need to reinstall (likely from a system or shared library side).
I recently installed Visual Studio 2013 Ultimate version on my machine. I'm just trying to create a sample windows form project and trying to open the designer / form by double clicking on Form1.cs and I'm getting this weird error message:
"the service microsoft.visualstudio.shell.interop.iselectioncontainer already exists in the service container"
My system is already having Visual Studio 2010 which is working smoothly from a long time. I then installed Visual Studio 2012 which was giving the same problem as above. So I went ahead with installing VS 2013 hoping that I might be able to get rid of this issue, but no use.
Once I click OK on the error windows, I can see the following "message" in the bottom Error List window:
"The file 'C:\Users\ABCD\Documents\Visual Studio 2013\Projects\WebSite1\WindowsFormsApplication1\Form1.cs' does not support code parsing or generation because it is not contained within a project that supports code."
I have spent 2-3 days searching various blogs like these, all of which talk about previous version of Visual Studio like VS 2005 / VS 2008:
https://connect.microsoft.com/VisualStudio/feedback/details/311949/the-service-microsoft-visualstudio-shell-interop-iselectioncontainer-already-exists-in-the-service-container
Form inheritance in Visual Studio 2008 doesn't work
I have even tried uninstalling and reinstalling VS 2013, again no use.
It would be really great if someone can help me out in fixing this.
I've just had the exact same error message.
After compiling the solution(F6 or Build->Build Solution) it worked fine for me.
To deal with your issue, please first make sure that you installed latest updates on your Windows 8 machine, and then repair VS2013.
During your repairing process, please temporally turn off your anti-virus/antispyware software and repair VS2013 with the Administrator privilege.
follow this link
The problem got resolved finally, after so many days and various frustrating tries to resolve the issue. I should thank Tim Atkins from Microsoft for helping me with resolving this issue.
Fix: When we tried 'gacutil /l system.design', we found that there were 3 variants of system.design; One from .Net 2.0 targetting MSIL, second from .Net 4.0 targetting x86 and last one also from .Net 4.0, but targetting MSIL.
On a working machine, there were only 2 entries, the .Net 4.0 one targetting x86 wasn't there. Hence we uninstalled this version using gacutil which did the magic. I was so relieved seeing the win forms popping up without any errors anymore :)
I changed the target framework from 4.5 to 4.6.1 and it fixed it for me. My assumption is sometimes when you change target framework back and forth and the process does not go through all the way (cancelling in the middle of changing it) - something happens that leads to this error. Hope that helps
I solved this be closing VS, deleting contents of the .vs folder where my solution is, restarting VS and recompiling.
Seems like one of those file/settings/caching problems that pop up now and then, might be after switching source branch.
VS2019, .net fw 4.6.2.
If your C drive (Where you are installing Visual Studio) does not have enough space, try moving some files from the C drive to another drives.
Seeing an issue when debugging in Visual Studio. All of the values under watch, and in the hover over window show up incorrectly. the only values that show properly, are values that are local to the method I am currently stepping through.
For example the watch value for 'this' when debugging shows the following under value
0x00000000ffac0388 { btnBack=0x00000000ffaccf20 btnReply=0x00000000ffacd200 btnForward=0x00000000ffacd420...}
some other variables show this, even though the variable is there.
error: 'this.foo' does not exist
The machine recently had windows 7 64 installed, since then this problem has occured.
Visual studio has been reinstalled on this machine, and we verified that the settings in visual studio were exactly the same as a different PC that is the same machine and config.
We finally figured out what the issue was. The devenv.exe was being set to run in xp compatibility mode (sp3). Doing a rebuild of the project after removing the compatibility mode fixed the issue.
Can you provide a bit more information to help us track down this problem. In particular
What operating system was installed before upgrading to Windows 7 64 bit?
Did you install Visual Studio before or after the upgrade?
Is there any other version of Visual Studio installed on the machine?
If you set your application to be x86 specific does the problem still repro?
What language is your code written in (assuming C#)?
When facing weird debugging issues, I find that deleting the solutions User Options file (.suo) usually fixes the problem. You will loose your bookmarks, breakpoints, any special exception handling, and so on.
If that fails then clear all your Visual Studio "temporary" files. Check out the "Clear Recent" script at http://missico.spaces.live.com/blog/cns!7178D2C79BA0A7E3!370.entry. Modify it for your own needs. For instance, I dislike Flash, so you may want to remove the call to ClearStupidFlash and the other non-Visual Studio calls. Clear your solution then "rebuild all".
If the problem still exists, then something else is going on.