[SOLVED] I've used Mono from Debian packages... it's old.
Building from the source, updates mono up-to-date and solves the problem. On Nov 20, 9:14 pm, [EMAIL PROTECTED] wrote: > Thanks for reply. > > I'm confused: my full story is - I've downloaded latest version of > mono for windows. Created VS2008 project using assemblies only from > mono 2.0 folder (not window's ones). Successfully developed one little > project (testing on windows) using DBLinq, then uploaded it onto > debian computer, with latest mono/mod_mono installed and got that > gettimestamp exception. > Later, when started investigating what's going on, found out that in > debian's GAC, all the DLLs are 2.0.0, and my window's ones are 2.0.5, > this small difference actually did the "job". Then I've tried to copy > those dlls onto debian server and restarted etc.... found out that the > function that is not found is in the mscorlib, which cannot be update, > since mod_mono's server checks it for version. and it wants version > nr. 65 (wich is 2.0.0), but there is version nr 69 (wich is window's > one, 2.0.5). > > Actually, when I checkout latest mono, it is 2.0.5 (it has most of > libraries numerated by that version) > > So my guess is that mod_mono is just not up to date (not released > yet). > > So this is why I'm confused... there is no any place which could be > somehow connected to "moonlight". At least if I did not miss something > during that "+exp" day. > > In anyways, DBlinq could have this ability to turn diagnostic on/off, > someones could want to turn it off when live-released,maybe. > > Thanks again for you attention. > > On Nov 20, 6:05 pm, Atsushi Eno <[EMAIL PROTECTED]> wrote: > > > Hello, > > > You likely have wrong reference to System.dll. For .NET 3.5 layer, you > > need so-called "2.0" profile. Version 2.0.5.0 is for moonlight (not mono > > 2.0 profile) and the correct version for 2.0 profile is 2.0.0.0. > > > Atsushi Eno > > > [EMAIL PROTECTED] wrote: > > > Hi all, > > > > I'm writing this post in order to share my "one-working-day" > > > experience of making those three parts of subject working together. > > > > Problem is: > > > - To have mono working with linq, you have to replace it's 2.0.0 > > > librarys with some 2.0.5 libraries. > > > - System assembly 2.0.5 uses Stopwatch, which's GetTimestamp method > > > uses mono's 2.0.5 mscorelib.dll > > > - latest mod_mono for debian requires mscorelib version 2.0.0 > > > - DBlinq's classes use Stopwatch. > > > > In a result it throws "cannot find getTimetamp method" when runing > > > through mod_mono+apache under debian. > > > > Solution: > > > - Replace all the usage of Stopwatch with s.c. MyStopwatch and it > > > starts working > > > > Proposal: > > > - use runtime diagnostics, only if some kind of LINQ_DEBUG derictive > > > is defined. > > > > PS: If I've missed something, and all these thoughts above are just > > > because of my lameness - I beg my pardon. > > > > J. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
