Please update to the latest version of Web Essentials 2012 after installing VS2012 Update 2

Please update to the latest version of Web Essentials 2012 after installing VS2012 Update 2

Rate This
  • Comments 2

After releasing ASP.NET and Web Tools 2012.2, which is also included in Visual Studio 2012 update 2, we’ve received a few customer feedback about their VS shows an error dialog saying:

An exception has been encountered. This may be caused by an extension.

You can get more information by examining the file 'C:\Users\<username>\AppData\Roaming\Microsoft\VisualStudio\12.0\ActivityLog.xml'.

When looking at ActivityLog.xml, the following error message may show up:

System.ComponentModel.Composition.ImportCardinalityMismatchException: Duplicate EditorFormatDefinition exports with identical name attributes exist. Duplicate name is LESSCSSVARIABLEDECLARATIONCLASSIFICATIONFORMAT

To solve this problem, one just need to update the “Web Essentials 2012” extension to the latest version.

What happened is author Mads (also PM in the Web editor team) graduated LESS and CoffeeScript feature from web essentials 2012 and put these feature officially in ASP.NET and Web Tools 2012.2 (see change log for version details).  So using an old version of Web Essentials will conflict with the newest version of VS2012 update 2.

Thanks for the support!  And keep enjoying Web Essentials!

Leave a Comment
  • Please add 2 and 4 and type the answer here:
  • Post
  • Not getting that... but I am getting the following on occasion:

    System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. Parameter name: span at Microsoft.VisualStudio.Text.ChangeTagger.Implementation.ChangeSet.ChangedSpans(Span span) at Microsoft.VisualStudio.Text.ChangeTagger.Implementation.ChangeTagger.<GetTags>d__10.MoveNext() at Microsoft.VisualStudio.Text.Tagging.Implementation.TagAggregator`1.<GetTagsForBuffer>d__16.MoveNext()

  • @Mgetz, thanks for reporting this.  Do you have a detailed repro step for that to happen?  It can happen with any editor as I've see the similar stack in our bug db for different editors and had been fixed for previous version of VS.  It's very likely this is something new.  Could you please help us log a connect bug with repro steps if you can?  Really appreciate it!  Thanks!

Page 1 of 1 (2 items)