Migrating .Net Framework Versions

[Brad_Hamilton]

AutoCAD 2010 VB.NET
I inherited a suite of AutoCAD VB.Net projects written for AutoCAD2008.
In My Project>References, some of the System reference files are pathed to...
c:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5
and others to...
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

Can someone help me understand framework versioning as it pertains to AutoCAD 2010 and what its effect is on code migration and sustainablity? Same with COM interop files; they seemed to be pathed all over the place - some with 'Copy Local' property set to TRUE and others to FALSE. If I reference a class dll from projects A, B and C, do A, B and C all need recompiling if the verison of the referenced class dll changes?

Although I think I have a good grasp of utilizing objects, sometimes I feel really stupid when it comes to these sorts of issues.

Any clues would be most appreciated.

[Anonymous]

The paths you show are for the 2.0 and 3.x versions of .NET.

The files for the two versions are not in the same location.

AutoCAD 2010 requires your project to reference .NET 3.5
assemblies because it is dependent on them.

--
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:6354860@discussion.autodesk.com...
AutoCAD 2010 VB.NET
I inherited a suite of AutoCAD VB.Net projects written for AutoCAD2008.
In My Project>References, some of the System reference files are pathed to...
c:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5
and others to...
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

Can someone help me understand framework versioning as it pertains to AutoCAD
2010 and what its effect is on code migration and sustainablity? Same with COM
interop files; they seemed to be pathed all over the place - some with 'Copy
Local' property set to TRUE and others to FALSE. If I reference a class dll
from projects A, B and C, do A, B and C all need recompiling if the verison of
the referenced class dll changes?

Although I think I have a good grasp of utilizing objects, sometimes I feel
really stupid when it comes to these sorts of issues.

Any clues would be most appreciated.

[Brad_Hamilton]

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

[Anonymous]

.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

[Brad_Hamilton]

Thanks again, Tony.

I'll assume that if they are "standard" windows .NET assemblies, and I leave the "Specific Version" property flag set to FALSE, and that, in addition, when the AutoCAD 2010 installation puts in its required .Netv3.5 files (if necessary), then all will be well.

[Anonymous]

Yes, you shoudn't change the specific version property, since
that would prevent your code from running with a service pack
applied if the minor version changed.

--
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:6357600@discussion.autodesk.com...
Thanks again, Tony.

I'll assume that if they are "standard" windows .NET assemblies, and I leave the
"Specific Version" property flag set to FALSE, and that, in addition, when the
AutoCAD 2010 installation puts in its required .Netv3.5 files (if necessary),
then all will be well.