Microsoft's behaviour is correct (maybe ECMA states it otherwise, but I don't know) because to fully specify an assembly you must either provide a qualified name like this (when the assembly resides in Global Assembly Cache):
System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 or just "System.Data" (when your assembly is in the same directory as *.exe) Actually there are some more options, like "codebase" hint in application config file. See MSDN for more information. For now, mono just loads assemblies from directory pointed by MONO_PATH variable. Jarek ----- Original Message ----- From: "Alfonso Ali Herrera" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 02, 2003 4:35 PM Subject: [Mono-list] Differences in behaviour in Assembly.Load() > Hi all, > > playing with the code in the xsp's dbpage2.aspx example i found that if i > declare System.Data as the assembly to load (in order to use > SqlConnection) it works ok in mono but in windows it give an error saying > that it can't download the System.Data assembly, copying System.Data.dll > to the application's directory fix the error. > > I'm very new to the .NET framework so, is the difference in behaviour ok? > if not whom (mono or Microsoft) is correct?? > > Ali > > _______________________________________________ > Mono-list maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/mono-list > _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
