User (Legacy) Posted November 24, 2006 Report Share Posted November 24, 2006 Hi All, I use ChartFX in .NET2 environment and just ran into the fact that all *.Adornments.dll assemblies contain references to the versions 1.0.5000.0 of the assemblies mscorlib and System.Drawing, i.e. reference .NET1 system assemblies. Could you comment on this? Regards, Slava Drozd. Link to comment Share on other sites More sharing options...
Software FX Posted November 24, 2006 Report Share Posted November 24, 2006 What tool are you using to check those references ? Here is what I see: // Assembly Reference mscorlib Version: 2.0.0.0 Name: mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 // Assembly Reference System.Drawing Version: 2.0.0.0 Name: System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a Is there any particular problem you are having ? -- Francisco Padron www.chartfx.com Link to comment Share on other sites More sharing options...
User (Legacy) Posted November 26, 2006 Author Report Share Posted November 26, 2006 Hi Francisco, Thanks for your reply. First of all - I´m not having any particular serious problems. The tool is very simple one - any viewer. Even if you open one of these dlls in notepad to view you would be able to find the following string: System.Drawing.Bitmap, System.Drawing, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a and if you look for something like "Version=1.0.5000.0" in any other ChartFX*.dll - you wouldn´t find any - you would find "Version=2.0.0.0". I suppose that these *.Adornments.dll were built with resources which refered to some .NET1 assemblies. I´m not going to say here that this is a bug or something, I just wanted you guys to pay attention to this fact - if you are intrested. Regards, Slava Drozd. "Software FX" <noreply@softwarefx.com> wrote in message news:dop7wT9DHHA.2096@webserver3.softwarefx.com... > What tool are you using to check those references ? > > Here is what I see: > > // Assembly Reference mscorlib > > Version: 2.0.0.0 > Name: mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 > > > // Assembly Reference System.Drawing > > Version: 2.0.0.0 > Name: System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a > > > Is there any particular problem you are having ? > > -- > Francisco Padron > www.chartfx.com > Link to comment Share on other sites More sharing options...
Software FX Posted November 27, 2006 Report Share Posted November 27, 2006 I did Check the adornment dlls (ChartFX.WinFOrms.Adornments.dll for example) , and they are not compiled with .NET 1.x, they are built with .NET 2.0, I do see this 1.0.5000 in notepad but I do not see it when using an apporpriate tool such as ILDASM or REFLECTOR, so I guess notepad is not a reliable tool for checking dependnecies. Here is what I get from ILDASM, please check on your end, you should get the same thing: // Metadata version: v2.0.50727 .assembly extern mscorlib { .publickeytoken = (B7 7A 5C 56 19 34 E0 89 ) // .z\V.4.. .ver 2:0:0:0 } .assembly extern ChartFX.WinForms.Base { .publickeytoken = (A1 87 8E 20 52 C0 8D CE ) // ... R... .ver 7:0:2515:41462 } .assembly extern System { .publickeytoken = (B7 7A 5C 56 19 34 E0 89 ) // .z\V.4.. .ver 2:0:0:0 } .assembly extern System.Drawing { .publickeytoken = (B0 3F 5F 7F 11 D5 0A 3A ) // .?_....: .ver 2:0:0:0 } .assembly extern System.Xml { .publickeytoken = (B7 7A 5C 56 19 34 E0 89 ) // .z\V.4.. .ver 2:0:0:0 } -- Francisco Padron www.chartfx.com Link to comment Share on other sites More sharing options...
Software FX Posted November 27, 2006 Report Share Posted November 27, 2006 Found it !!!! What you see is actually not a reference but an internal resource generated with .NET 1.x, this is however harmless as the resources are loaded using the .NET Framework the application is using but I guess it will be cleaner to convert these to .NET 2.0. -- Francisco Padron www.chartfx.com Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.