Hank Fay <> wrote: > Aside from the difference in getting the CLR version installed > (20-40meg vs. 5 meg), and the lack of backward compatibility, .Net > also gives developers the ability to _turn off_ backward > compatibility, which appears to be what happened here. > > To claim, with an exclamation regarding the presence of bovine > excrement, that there is no difference, disregards the obvious, > important, and noxious differences. > > BTW: it's not a VS2005 vs. VS2003 difference, really. It's about the > .Net version (which can be accessed independently of VSxxxx, q.v. > ReSharper, Notepad, etc.)
Ok, lets cut through some FUD. Yes you can reference the assembly by its strong name. Strong-named assemblies consist of the assembly's identity: 1.- The simple text name of the assembly. 2.- The version number of the assembly. 3.- The culture information, if it is provided (optional). 4.- A public key for the client. 5.- A digital signature. So were there multiple versions in your GAC? I am guessing that your attempting to use one from VFP and the other is rearing it's ugly self? It's not working properly and the whole process is hitting the bit bucket? But then I really don't remember what your issue was in the beginning. So what I have said may have no real value? Sorry. Stephen Russell DBA / Operations Developer Memphis TN 38115 901.246-0159 http://spaces.msn.com/members/srussell/ -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.3/374 - Release Date: 6/23/2006 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
