And now that I'm finding out that I can no longer compile a program for 2007
just because I also have 2008 installed, it's starting to look like lisp &
vba are the only ways I can continue coding for multiple versions. I had
thought the the .NET framework was supposed to HELP in this regard. But,
thanks to Adesk throwing a bunch of version dependent files into the
Autodesk_Shared folder, working with code for a previous version is nearly
impossible. Sure, I can still use it in 2007, but anyone else who has JUST
2007 is not able to run it, as it gets compiled with the 2008 libraries
(nope, can't even reference the older ones). Just plain dumb.....IMHO.
So it's looking like I've wasted a geat deal of time moving to the .NET
format. While it looked promising, this version specific crappola is for the
birds.
Now if anyone would care to share how I'm completely misguided, I'm still
willing to listen......
On a separate, but related, note:
Why do the docs, Intellisense, VBA & VB.NET all say/suggest/use some
properties, but C# does not? I've asked about this previously but only today
found a workaround (thanks Sinc). Specifically, get a Point object, Find the
PointGroup(s) it belongs to, attempt to get the PointStyle used by one of
the groups.
You would think (and can do in VB.NET) that this would work:
string strName = oPointGroup.Pointstyle.Name;
But nope, all you get is a Build error.
In order to access the PointStyle, one must use this format:
string strName = oPointGroup.get_Pointstyle().Name;
which is not Intellisense friendly, nor is it covered in the docs.
I would really like to use this C#.NET more, but things like this just work
to push me away.
Thanks,
Jeff
"Jeff Mishler" wrote in message
news:5515982@discussion.autodesk.com...
So after banging my head against the desk for far too long, I've come to the
conclusion that the .NET wrappers are not up to speed, or, if they are, the
documentation on how to implement them is not.