madskristensen / WebEssentials2013

Visual Studio extension
http://vswebessentials.com
Other
944 stars 252 forks source link

Visual Studio crashes when opening VS Multi-Device Hybrid App project #1390

Open jmatthiesen opened 10 years ago

jmatthiesen commented 10 years ago

After installing Web Essentials 2013, Visual Studio crashes for me whenever I try to open a project built using the new Multi-Device Hybrid App tools (http://msdn.microsoft.com/en-us/vstudio/dn722381.aspx). The error in the event log isn't very useful, but I confirmed this is Web Essentials because the error is fixed if I disable the extension.

From the event log: Faulting application name: devenv.exe, version: 12.0.30723.0, time stamp: 0x53cf6f00 Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532943a3 Exception code: 0xe0434352 Fault offset: 0x00011d4d Faulting process id: 0x3534 Faulting application start time: 0x01cfb5bb26772bdb Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll Report Id: 6a65770b-21ae-11e4-8263-082e5f203d82 Faulting package full name: Faulting package-relative application ID:

susanshi commented 10 years ago

+1

sureshja commented 10 years ago

:+1:

andersrosten commented 10 years ago

I'm experiencing the same issue except with a solution with a classlibrary and web applicaiton. The problem started after updating VS to Update 3 and WE version 2.2.7.

The activitylog does not state anything WE related other than multiple copies of these lines: 736 Warning PkgDef encountered data collision in section 'HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0_Config\ToolsOptionsPages\Web Essentials' for value '' VisualStudio 2014/08/12 10:41:36.258 737 Warning PkgDef encountered data collision in section 'HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0_Config\ToolsOptionsPages\Web Essentials' for value 'Package'

When WE is disabled the solution loads fine.

Update Found out the 2.2.7 version from the nightly build was older than the official 2.3, so uninstalled and installed the officical 2.3 version and now the solution loads again. Chosing re-compile all sass files does not work however, and results in a lot of the following lines in the output window.

12-08-2014 12:57:38: Something went wrong reaching: http://127.0.0.1:11568/?service=SCSS&sourceFileName=C:%5CProjects%5CGnol%5CDevelopment%5CCode%5CS... 12-08-2014 13:03:11: SCSS: _attach.scss compilation failed: The service failed to respond to this request Possible cause: Syntax Error!

Don't know if it's related or should have its own issue?

am11 commented 10 years ago

It may be related to https://github.com/madskristensen/WebEssentials2013/issues/1182. As you can see, its a lost cause to keep track of so many project systems, unless they (the project systems groups) all abide by some unified set of interfaces for automation devs..

@andersrosten, I hope 2.3.2 fixed the SASS issue you are having? Otherwise (if you are sure that there is no syntax error && you are using syntax which is supported by libsass), then the error might be coming from the upstream (node-sass). The more easy approach would be to share some code which chokes compilation, so we can test. See https://github.com/madskristensen/WebEssentials2013/blob/master/CONTRIBUTING.md#bug-reports.