Comments on: MEF support for the Output Window in Visual Studio 2010 http://blog.280z28.org/archives/2009/11/79/ Because it's easier than editing the HTML by hand. Wed, 05 Oct 2011 19:39:44 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Robert http://blog.280z28.org/archives/2009/11/79/comment-page-1/#comment-29723 Robert Wed, 05 Oct 2011 19:39:44 +0000 http://blog.280z28.org/?p=79#comment-29723 <p>Looks like you're building an ANTLR VS2010 plug-in that would be really useful; are you willing to share/sell it?</p> Looks like you’re building an ANTLR VS2010 plug-in that would be really useful; are you willing to share/sell it?

]]> By: Gaspar Nagy http://blog.280z28.org/archives/2009/11/79/comment-page-1/#comment-17084 Gaspar Nagy Tue, 21 Sep 2010 11:59:59 +0000 http://blog.280z28.org/?p=79#comment-17084 <p>This was very useful, thanks!</p> <p>For me, VS2010/MEF was unable to resolve the OutputWindowService. I had to change the property type of the GlobalServiceProvider field from IServiceProvider to SVsServiceProvider (Microsoft.VisualStudio.Shell namespace). [Import] public SVsServiceProvider GlobalServiceProvider;</p> <p>(Also I had to comment out the code contracts part, because I did not wanted to enable contracts in my project.)</p> This was very useful, thanks!

For me, VS2010/MEF was unable to resolve the OutputWindowService. I had to change the property type of the GlobalServiceProvider field from IServiceProvider to SVsServiceProvider (Microsoft.VisualStudio.Shell namespace). [Import] public SVsServiceProvider GlobalServiceProvider;

(Also I had to comment out the code contracts part, because I did not wanted to enable contracts in my project.)

]]>