Error in Visual Studio 2015 Update 1 CTP

[delie]

Apologies for flagging this if you're not testing in the 2015 Update 1 CTP yet, but I'm getting an error upon opening a Jade file in the editor.

It seems to be complaining that "contentTypes" is not a key. Occurs in the constructor for Microsoft.NodejsTools.ClassifierProviderMetadata

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at System.Collections.Immutable.ImmutableDictionary2.get_Item(TKey key)
 at System.Collections.Immutable.ImmutableDictionary2.System.Collections.Generic.IDictionary<TKey,TValue>.get_Item(TKey key) at Microsoft.NodejsTools.ClassifierProviderMetadata..ctor(IDictionary2 values)
 --- End of inner exception stack trace ---
 at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
 at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
 at Microsoft.VisualStudio.Composition.MetadataViewClassProvider.CreateProxy(IReadOnlyDictionary2 metadata, IReadOnlyDictionary2 defaultValues, Type metadataViewType)
 at Microsoft.VisualStudio.Composition.ExportProvider.GetStrongTypedMetadata(IReadOnlyDictionary2 metadata, Type metadataType) at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.GetValueForImportElement(RuntimePartLifecycleTracker importingPartTracker, RuntimeImport import, RuntimeExport export, Func3 lazyFactory)
 at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.GetValueForImportSite(RuntimePartLifecycleTracker importingPartTracker, RuntimeImport import)
 at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.RuntimePartLifecycleTracker.<CreateValue>b__10_0(RuntimeImport import)
 at System.Linq.Enumerable.WhereSelectArrayIterator2.MoveNext() at System.Linq.Buffer1..ctor(IEnumerable1 source) at System.Linq.Enumerable.ToArray[TSource](IEnumerable1 source)
 at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.RuntimePartLifecycleTracker.CreateValue()
 at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.Create()
 at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.MoveNext(PartLifecycleState nextState)
 at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.MoveToState(PartLifecycleState requiredState)
 at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.GetValueReadyToExpose()
 at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.<>c__DisplayClass15_0.<GetExportedValueHelper>b__0()
 at Microsoft.VisualStudio.Composition.DelegateServices.<>c__DisplayClass2_01.<As>b__0() at System.Lazy1.CreateValue()
--- End of stack trace from previous location where exception was thrown ---
 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
 at System.Lazy1.get_Value() at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.InvokeMatchingFactories[TExtensionInstance,TExtensionFactory,TMetadataView](IEnumerable1 lazyFactories, Func2 getter, IContentType dataContentType, Object errorSource)

[mousetraps]

We'll try to investigate this before our next release

Just so I understand the problem better... does it occur with every jade file? Or only when there is specific text in the editor?

[delie]

Hmm, good question. Unfortunately, since my original post I tried to uninstall/reinstall the NodeJS tools, but it seems I can no longer install at all. I'm using Visual Studio Community 2015, version 14.024606.01 Update 1 CTP.

I've tried installing NTVS 1.1 RC2.1 VS 2015, and NTVS.Dev.2015-10-20.VS.2015, but both of them are coming up with a "Visual Studio 2015 is required" error.

I only upgraded to the Update 1 CTP, because I wasn't able to save my tab settings in the text editor for Jade files, but looks like it made matters worse :)

I think I originally installed the Node JS tools on top of the non Update-1 version of VS Community 2015. I then updated VS Community 2015 to VS Community 2015 Update 1 CTP, and that's when I started getting the Jade error in Node JS tools. I think it happened with any Jade file, but can't re-test it at the present time given my dev environment is now different to how it was originally.

[delie]

If there's any other tests I can do in VS2015 Update 1 CTP let me know and I'll be happy to help

[mousetraps]

@billti fyi looks like this issue is still occurring in the latest vs update bits.

[billti]

I just installed the VS2015 Update1 RC and the latest NTVS build, and got this issue also. Deleting the MEF cache and running devenv /setup to recalculate didn't resolve it. The MEF error log only contains events unrelated components.

Not sure what is causing this to happen now... but we'll need to get it resolved before we ship 1.1 :-( Investigating...