.NET 3.5 is an extension to .NET 2.0, which is why you don't see
the same files in different locations.
I don't really have time to explain 'what's what and where do they
come from', sorry.
The compile process does not extract anything. The targeted
framework must be installed on the target system, and that's
about it.
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD
Supporting AutoCAD 2000 through 2010
http://www.acadxtabs.com
Email: string.Format("{0}@{1}.com", "tonyt", "caddzone");
wrote in message news:6357139@discussion.autodesk.com...
Thanks Tony.
After more digging, I notice that the ...\v2.0.50727 assemblies have no
equivalents in the differently pathed ..\v3.5 folder. So, what's what and where
do they come from?
Did not AutoCAD 2010 install some v3.5 assemblies and why isnt there a common
location for all framework files?
Finally, for now ;), does the compile process extract what it needs from the
references? Or does the machine that runs the app have to have the same pathed
assemblies? An install?
Just not as easy as the "drop the lisps file in place and off you go",
especially in a larger organization with an increasingly more constricted IT
structure.
Edited by: Brad_Hamilton on Mar 18, 2010 4:19 PM