04-06-2006 08:13 AM
04-07-2006 12:59 PM
04-07-2006 01:49 PM
Pat P,
Thanks for the feedback. I'm using VS.NET 2003, .net FW 1.1, TestStand 3.5.
Jason
06-07-2006 06:29 PM
06-08-2006 06:52 AM
06-08-2006 09:52 AM
David makes a good point. Be aware that even if you are using version 2.0 of the .NET Framework, mscorcfg gets installed with the SDK.
- Eric
11-08-2006 05:34 AM
Well thanks to those above for providing this information. I've been puzzling over this for two days, and have even blanked the HD and reinstalled Windows.
I'll add the full error message so that hopefully more people will find this with a search (I didn't find this thread yesterday):
Error while accessing the .NET assembly.
Could not load file or assembly 'mscorcfg, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
I'm in a position where I am a TestStand developer, but not a .net developer - I'm given .net DLLs by other people here. I now know I need the .net SDK as a TestStand developer. Do I need to install this SDK on deployment systems, or is it required only for TestStand development?
I would suggest that NI need to include this SDK in their TestStand development system installer if it's a prerequisite, or at least point the user to it.
11-08-2006 07:25 AM
11-08-2006 08:30 AM
11-08-2006 08:41 AM - edited 11-08-2006 08:41 AM
...and a further question:
If I make a sequence that calls .net steps and give this sequence to other developers, what pre-requisites are there for running my sequence on another devlopment system? In this case, the sequence needs to be executed, but the .net steps do not need to be edited.
The chain here is that some others produce .net DLLs. I integrate these into TestStand. I pass my sequences to others, who use TestStand and LabVIEW. These people need to be able to execute my sequences (under the development system) that call the .net DLLs.
Message Edited by Sean on 11-08-2006 02:41 PM