VS 2013 Update 2
Web Essentials 2013 for Update 2
When I open a web project I get an error message from VS telling me an exception has occurred. When I check the ActivityLog.xml file I see the following error, many times
System.TypeLoadException: Could not load type
Microsoft.Css.Extensions.CssVariableDeclaration
from assembly Microsoft.VisualStudio.Web.Extensions
The call stack ends at MadsKristensen.EditorExtensions.Css.ColorTagger.GetColors(CssTree tree, SnapshotSpan span)
Any one know how to get past this one?
I have tried reinstalling Web Essentials and repairing VS2013
Thanks
Related
There are several similar questions but no one of them actually works for me.
I wanted to make a .Net Core application (API) but as I said the build fails (even with the default application). If I try to continue, IIS shows "Error 500.0 - ANCM In-Process Handler Load Failure".
Tried everything, from restarting VS to deleting and reinstalling it but it does not work. It instead works on a virtual machine but have no idea what's the difference. What might I do?
Microsoft Visual Studio Community 2019
Version 16.8.3
I've the same error but in an ASPNET u need see the errors in the build/debugging output
I've an error but that don't show
You need to find the error within the logs
My error was an update Panel
////
EDIT:
Try this: Select Entire Solution and Build Only to show the Errors
I am trying to open a solution on VIsual Studio 2017. (The project was originally developped in VS 2012). I managed to open the project and to work on it before. But this morning I get :
An exception was encountered while constructing the content of this frame. This information is also logged in "C:\Users\myName\AppData\Roaming\Microsoft\VisualStudio\15.0_fa6f4449\ActivityLog.xml
The project loads in VS, but it does not recognized the Entity Framework Models correctly. Any idea on what is happening?
For further reference (maybe it'll help someone in the future), I have solved this error by updating Visual Studio. It was apparently an IDE bug. (More info here)
Yesterday I studied a little MVC5 before bed.
Today, I open Visual Studio 2013 and while loading, the following exception occurs:
Exception Details
System.ArgumentNullException was unhandled
Message: An unhandled exception of type 'System.ArgumentNullException' occurred in mscorlib.dll
Additional information: Buffer cannot be null.
Parameter name: buffer
I have already repaired Visual Studio and nothing has changed.
Does anyone know what's going on?
The Update 5 worked for me. However you need to be part of Dev Essentials in order to download this update.
https://my.visualstudio.com/Downloads?q=Visual%20Studio%202013%20Update%205
Appears to be fixed now, although I see no confirmation on https://social.msdn.microsoft.com/Forums/en-US/46728392-212b-405e-aea0-2ab02f91cd1f/visual-studio-2013-crashes-on-startup?forum=visualstudiogeneral
I'm running VS2013 U3 and able to startup without issue. A colleague is able to run VS2013 as well.
My system got shut down anyhow and after this I am not able to open projects in visual studio 2013. I tried creating new project and it was opening and running fine untill I added a new class library to it. Once my new solution has two project, it started creating same problem. Visual studio is not opening solution with message "Microsoft Visual Studio 2013 has stopped working". I tried to debug this and getting below error:
"System.InvalidOperationException was unhandled
Message: An unhandled exception of type 'System.InvalidOperationException' occurred in Microsoft.VisualStudio.Editor.Implementation.dll
Additional information: Attempting to activate an adapter in state TextViewInitializing"
I tried google to search the solution but not getting anything relevant. I tried clearing temp files but no success. I cleared bin and debug folder but still no luck. Do you have any solution for this.
I recently installed Xamarin. I experienced no issues with it for about a week. Now, when i load visual studio I get an alert that says:
The 'InspectorPackage' package did not load correctly.
The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file
'C:\Users{redacted}\AppData\Roaming\Microsoft\VisualStudio\14.0\ActivityLog.xml'.
Restarting Visual Studio could help resolve this issue.
Continue to show this error message?
Restarting Visual Studio does not resolve this issue.
Upon inspecting the xml file, I find:
<entry>
<record>503</record>
<time>2017/02/15 15:33:56.686</time>
<type>Error</type>
<source>VisualStudio</source>
<description>LegacySitePackage failed for package [InspectorPackage]Source:
'' Description: Not implemented
(Exception from HRESULT: 0x80004001 (E_NOTIMPL))
System.NotImplementedException: Not implemented
(Exception from HRESULT: 0x80004001 (E_NOTIMPL))
at EnvDTE.Project.get_FullName()
at Xamarin.Inspector.VS.VSAgentExecutionTarget..ctor(Project proj)
at Xamarin.Inspector.VS.VSInspectorSession.CreateAgentExecutionTarget()
at Xamarin.Interactive.IdeSupport.InspectorSession.Prepare()
at Xamarin.Inspector.VS.InspectorPackage.RefreshInspectorSession()
at Xamarin.Inspector.VS.InspectorPackage.Initialize()
at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp)
</description>
<guid>{0FCBA9C6-0554-418C-8B79-FF2ED7DC658D}</guid>
<hr>80004001 - E_NOTIMPL</hr>
<errorinfo></errorinfo>
</entry>
What can I do to fix this?
This error seems to only appear when you have multiple startup projects in a solution.
I reproduced it by creating an empty solution with two empty console projects. When only one is set as startup everything works fine. However, when setting both as startup this error pops up.
I also came across this bug where the last post on 14 Jan 2017 states that the upcoming version 1.1 release will fix this issue: https://bugzilla.xamarin.com/show_bug.cgi?id=49417
You can check your version in the about box in VS. On VS2015 it is Help | About Microsoft Visual Studio and I reckon it is the Xamarin Inspector Support entry. Mine is at 1.0.0.0 so I assume I'll have to wait for the upcoming release :)
update:
Oddly enough, an update just arrived for the Xamarin Inspector (less than 30 min after answering). The first load of my test solution still popped up with the error but after that it seems fine.
update (28 Feb 2017):
I am still experiencing the issue with the following version:
Xamarin Inspector Support 1.1.2.0 (cdc01b9f4466b6dcc3095828824a12d041c9f55e)
Adds support for inspecting Xamarin and WPF apps.
This is what i did and it worked for me:
1) go to the path of Visual Studio and delete everything in that folder
(this will delete you visual studio set up ) Visual Studio wont work after this
C:\Users\<username>\AppData\Local\Microsoft\VisualStudio
2) uninstall Visual Studio. And install it again.
If this didn't work look around for xamarin files in that folder and delete everything inside.