TheSwamp
Code Red => .NET => Topic started by: Viktor on October 30, 2009, 03:48:53 PM
-
Well, we live and learn, the hard way sometimes. I developed my .net application targetting 2010 and ended up using some 2010 api changes without knowing it. For example I used the Internal.Utils.SelectObjects, which is apparently new and I used TextStyleId to set the textstyle objectid. So now I'm looking at ways to downgrade these things to 2009 and I'm stuck with these 2 issues.
1. I can't seem to find a way to select/highlight objects without using interop.
2. How do I check for current application version? so that I can test and use the proper property since TextStyle is not availablein 2010 and TextStyleID is not available in 2009.
Thanks,
Viktor.
-
Well, the textstyle thing can be solved a number of way i guess, I chose this one because I do this in my code in other places so not to introduce anything new. Any performance issues with this approach?
Dim Attpdc As PropertyDescriptorCollection = TypeDescriptor.GetProperties(attref)
If Autodesk.AutoCAD.ApplicationServices.Application.Version.Major <= 17 Then
Dim pd As PropertyDescriptor = Attpdc("TextStyle")
pd.SetValue(attref, ValidTR.ObjectId)
ElseIf Autodesk.AutoCAD.ApplicationServices.Application.Version.Major >= 18 Then
Dim pd As PropertyDescriptor = Attpdc("TextStyleId")
pd.SetValue(attref, ValidTR.ObjectId)
End If
-
selecting objects is bread and butter for .net api, interop not needed.
Do a search on this site for select to find lots of examples.
Your handling of the versions seems good to me, I do version forks in several places.
-
selecting objects is bread and butter for .net api, interop not needed.
Do a search on this site for select to find lots of examples.
Your handling of the versions seems good to me, I do version forks in several places.
Just to verify, cause I'm not finding much about this, I'm talking about creating a visual selection on the screen, an alternative to highlighting because highlighting is not always very visible. I want to click a button and show a selected object on screen.
-
i goofed, didn't reference the internal dll.
-
To clarify for anyone following along
Prior to AC2010, acmgdinternal.DLL required referencing for access to the Autodesk.AutoCAD.Internal.<..> namespaces.
In AC2010 acmgdinternal.DLL no longer exists, the contents has been included with the acmgd.dll Module.
-
Yea, thanks for clarifying this, but this brings me to the next question, sooooo how do you build your dll so that both version can use the internal namespace? It seems that if I compile with 2010 then any function that calls internal functions crash the program, and when i compile with 2009 and reference the acmgdinternal.dll then it crashes on 2010 but works fine on 2009. So what do I do?
-
Personally, I'd build a destinct dll for each version.