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

VS2012 VCProjectEngine.VCDebugSettings.ApplicationCommand. Seriously?

$
0
0

Hi everybody.

The VCDebugSettings.ApplicationCommand attribute was in the Visual Studio SDK forever. Or at least from the version 2005. After moving to 2012, I noticed that this particular attribute is giving me some grief. Long story short: I traced it to this class:

.class public auto ansi beforefieldinit Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCDebugSettingsShim
       extends [mscorlib]System.Object
       implements [Microsoft.VisualStudio.VCProjectEngine]Microsoft.VisualStudio.VCProjectEngine.VCDebugSettings,
                  Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.IVCDebugSettingsImpl,
                  [mscorlib]System.IDisposable
To my surprise I found that the attribute in question was implemented like this:

.method public hidebysig newslot specialname virtual final 
        instance string  get_ApplicationCommand() cil managed
{
  // Code size       6 (0x6)
  .maxstack  8
  IL_0000:  newobj     instance void [mscorlib]System.NotImplementedException::.ctor()
  IL_0005:  throw
} // end of method VCDebugSettingsShim::get_ApplicationCommand

Note that the MSDN library doesn't say anythiyng about this attribute being depricated:http://msdn.microsoft.com/en-us/library/microsoft.visualstudio.vcprojectengine.vcdebugsettings.applicationcommand(v=vs.110).aspx

I have two questions:

1. What is wrong? The docummentation or the code? I prefer the later to be fixed rather than the former.

2. Now what? Is there any alternative to using this attribute?

Meanwhile my 2012 integration remains brocken. Any help will be greatly appreciated.



Viewing all articles
Browse latest Browse all 4410

Trending Articles



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