Reference in Visual C++ .NET Measurement Studio ends in catatstrophic failure?

[Jeffray G]

Stack Trace:

   at Microsoft.VisualStudio.VCProjectEngine.VCReference.get_FullPath()
   at NationalInstruments.DotNET.ComponentWizard.AddIn.b(VsProject )
   at NationalInstruments.DotNET.ComponentWizard.AddIn.a(Project )
   at NationalInstruments.DotNET.ComponentWizard.AddIn.OnOpened(Object sender, EventArgs e)

This failure occurs when I open the MS Visual C++ .NET 2003 application. Is there a bad path to the VCProjectEngine? Is the Project unable to open the object reference? If so, how do I correct this problem, other than not using reference?

[Jeffray G]

Additional information to the question I submitted:

c:\program files\microsoft visual studio .net 2003\common7\ide\publicassemblies\MICROSOFT.VISUALSTUDIO.VCPROJECTENGINE.DLL

VC Project Engine Library File version: 7.0.5000.0

[Gavin F]

Hi Jeffray G,

Which version of Measurement Studio are you using?
You might be running into a known issue with having only VB.NET installed.  A fix is available, and it's discussed in this Knowledgebase:

Measurement Studio Add-in Error when Only Microsoft Visual Basic .NET Is Installed with Microsoft Visual Studio .NET
http://digital.ni.com/public.nsf/websearch/879DED7B1EAFF49886256F0F0058A19E?OpenDocument

[Jeffray G]

Gavin F.,

I am not having the same problem but similar. You can view the screen shot of the Error message here: http://jeffraygspot.blogspot.com/ I am using Measurement Studio version 7.1.0.306. I am not using just VB .NET but VC++ .NET in my project. I hope the screen shot helps.

Jeffray G.

[Gavin F]

Hi Jeffray G,

Thanks for the screenshot.  I've searched for causes of this catastrophic error.  It looks like some of these have been caused by trying to use an ActiveX Control as if it were an ActiveX Server. 

I would like to try to open your project here.  You could post it here, or if you give me permission to get your email address from your forum profile (assuming it's up to date), then I can send you an email that you can reply to.

[Jeffray G]

Gavin F,

For the sake of moving on, I decided to take the sensible approach. Instead of trying to include the part of the project that was using Measurement Studio in my project, I have instead made a DLL of the needed functionality in its own project and forged on ahead. I can't afford to get behind the curve on this project so I took the alternative path. Thanks for your efforts but I have already deleted the old project and gone on to create two new projects instead.

Jeffray G.

[Gavin F]

Hi Jeffray G,

I understand.  If you ever see the error again, we would be interested in checking out the project.