Quantcast
Channel: Visual Studio Integrate forum
Viewing all articles
Browse latest Browse all 4410

Visual Studio 2013 not loading extension when debugging in experiemental instance

$
0
0

For Visual Studio 2010 I created a super simple VSIX extension which implemented ITaggerProvider. When VS 2012 came out I updated the vsix manifest to include it as well, but with VS 2013, the vsix manifest changed to version 2, which allowed for no max version. To make use of this, in VS 2013 I created a new VSIX project (but in the original solution), set the manifest to have an install target of [12.0,], copied the original source code (there's only one small file), and compiled.

I set my new project as the default launch project, but when debugging, no break points get hit. I check the Extensions and Updates menu item and my new extension is listed there, but it doesn't seem to be having any affect, and since the break points are even loading, I suspect that my visx file isn't getting loaded by the experimental instance.

Did something change between VS 2012 and VS 2013 that would have broken loading an ITaggerProvider?

Here's all of the code that I think is relevant (TextBufferTracker is my own class):

[Export(typeof(ITaggerProvider))]
[TagType(typeof(ITextMarkerTag))]
[ContentType("code")]
internal sealed class CodeTaggerProvider : ITaggerProvider
{
	public ITagger<T> CreateTagger<T>(ITextBuffer buffer) where T : ITag
	{
		Func<ITagger<T>> sc = delegate()
		{
			return new TextBufferTracker(buffer) as ITagger<T>;
		};
			return buffer.Properties.GetOrCreateSingletonProperty<ITagger<T>>(sc);
	}
}


Viewing all articles
Browse latest Browse all 4410

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>