Hi,
after all that trouble with ActiveX versions and broken wires (known also to all Excel programmers) I believed in Autodesk's AutoCAD2010 manual stating that at least the .NET interface won't change between the 32-Bit and 64-Bit version. So I'm trying to translate my working ActiveX application to .Net
Well, so far at least my LabVIEW8.61 test application won't work on the 64-Bit machine.
So I installed the trial LV8.61 and LV2009 there and I can't even select the .Net Constructor. The field simply stays empty! For all objects. Even the "This class contains no public constructors." message doesn't appear.
Picking any of the other Assemblies (17.1.51.0 or 17.0.54.0) doesn't help either. I can see the constructors of the "Autodesk.AutoCAD.Interop.Common" assemblies though, or some other assemblies like "System", but they don't give me access to what I want, don't they (the ModelSpace)?

Yes, I know: Could be a thousand reasons, including intrinsic XP-64 DotNet problems or AutoCAD's mistakes, but would be nice to know that there's nothing we can do in LV!
Hi to Brian Tyler on Re: Constructor of .NET class not available in LV 8.20 - is this a another too long string in the 64-Bit system?
Hi to Jonathan N on Re: .NET constructors don't show up in LV 8.5 - seems I don't have the mscorcfg.msc for .Net3.5 on neither machine. But than this is not a network problem is it?
By the way: How do you reference foreign threads here?
Thanks
Jannis