tl;dr

You need to update Web Essentials 2013 to version 2.2. If not, Visual Studio will crash. Download now.

Before Visual Studio 2013 Update 3

The upcoming release of Visual Studio Update 3 has API changes in some of the components that Web Essentials is extending. Those changes are not compatible with the current version of Web Essentials and will cause VS to crash after upgrading to Update 3. To be fair, those APIs were never public to begin with, so I was taking a chance when I was using them in Web Essentials.

If you are currently using Web Essentials 2.1 for Visual Studio Update 2, you should see this dialog show up the next time you open Visual Studio.

Web Essentials update notification

This is the first time this notification feature has been used after introducing it in Web Essentials 2.1. Good thing we did.

It’s important that you install this update immediately. You don’t have to restart Visual Studio – it’s enough that you just install the update. If not, you might forget to do it before you install Visual Studio Update 3. So go do it now.

It turns out to be good timing, since we have added some cool new features in version 2.2. Here’s a list of a few of them:

This is unfortunately the price we have to pay to be on the cutting edge. Lesson learned and we’ll do our best to make sure this doesn’t happen again. It’s not a guarantee since Web Essentials will continue to use APIs that are unsupported by Microsoft. That’s the only way we can add all those cutting edge features.

Download Web Essentials 2.2

Comments

Sam

I installed WE 2013 2.2 for VS2013 Pro Update 2 and now I get this: Application: devenv.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ComponentModel.Composition.CompositionException Stack: at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__4(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

Sam
James

Yes getting the same thing as Sam with VS2013 Pro Update 2. Have tried repairing VS2013 Pro Update 2 (just in case) and then re-installing Web Essentials 2.2. Visual Studio opens ok but as soon as I open one of my existing projects Visual Studio crashes. If I debug using VS2012 (can't use 2013 as it crashes also) I get the following error: The composition produced a single composition error. The root cause is provided below. Review the CompositionException.Errors property for more detailed information. 1) No exports were found that match the constraint: ContractName MadsKristensen.EditorExtensions.Compilers.ProjectCompiler RequiredTypeIdentity MadsKristensen.EditorExtensions.Compilers.ProjectCompiler Resulting in: Cannot set import 'MadsKristensen.EditorExtensions.BuildMenu.Compiler (ContractName="MadsKristensen.EditorExtensions.Compilers.ProjectCompiler")' on part 'MadsKristensen.EditorExtensions.BuildMenu'. Element: MadsKristensen.EditorExtensions.BuildMenu.Compiler (ContractName="MadsKristensen.EditorExtensions.Compilers.ProjectCompiler")MadsKristensen.EditorExtensions.BuildMenu

James
Mads Kristensen

The build found here works fine http://vswebessentials.com/webessentials2013.vsix Sorry for the bad build

Mads Kristensen
Jeff Dannel

I installed the update above but the Minify JavaScript File(s) is not working now.

Jeff Dannel
Mads Kristensen

@Jeff, can you open a bug on https://github.com/madskristensen/webessentials2013/issues please?

Mads Kristensen
Jeff Dannel

Just installed the fix - Working great. Thanks !

Jeff Dannel
Andrey Taritsyn

Hello, Mads! I don't quite understand, how I can enable AutoPrefixer-optimizations for LESS- and Sass-assets?

Andrey Taritsyn
Paul Huizer

Hi mads, I really enjoy the way webessentials extends visual studio to make it even more efficient and powerful. As a scratch-your-own-itch project, I decided to write-up a simple package to extend visual studio with all kinds of goodness like grunt, gulp, sass compilers and so on ... Have a look: https://github.com/PaulHuizer/VsCommandBuddy Looking forward to your feedback...

Paul Huizer
Ivan

Hi. I've just created wp 8.1 JS application and got following: http://social.msdn.microsoft.com/Forums/getfile/485344 Less file compiles into css (I've looked in the explorer) but VS doesn't show it. How to fix this?

Ivan
Mads Kristensen

@Andrey, you must do that in Tools -> Options -> Web Essentials -> CSS @Paul, that sounds exciting. I'll take a look later today. @Ivan, please open a bug on the Web Essentials issue tracker https://github.com/madskristensen/WebEssentials2013/issues

Mads Kristensen

Comments are closed