Tony, Check the image base value that is specified in the project settings (I cannot remember where it is at exactly). I noticed while using the solution task before, that Visual Studio will ignore some invalid values when it builds, but the solution task uses them all.
I recommend resting any option to its default value (unless you changed it on purpose). When I upgraded from VS.NET 2003 to VS.NET 2003 I think that some of my project settings got clobbered. I had to change several settings back to their defaults. -Scott -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 17, 2003 11:24 AM To: [EMAIL PROTECTED] Cc: Scott Ford Subject: RE: [Nant-users] Problem with solution task Hi Scott I tried with build of 2003-12-13 but with the same results. Some further investigation revealed the following: The main difference between the IL file (generated with ildasm) of the working (VS built) EXE and the "broken" EXE appears to be the ".imagebase" value. Working EXE - .imagebase 0x11000000 Broken EXE - .imagebase 0x85210000 If I edit the generated IL file of the broken EXE (change .imagebase to 0x11000000) and then generate the EXE (using ilasm) the resultant EXE seems to work fine. I am not sure what to try next - any suggestions ?? Regards, Tony "Scott Ford" <[EMAIL PROTECTED]>@lists.sourceforge.net on 15/12/2003 06:37:20 PM replied : Tony, Many solution task bugs have been fixed since then. Did you try this in the nightly build? -Scott -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, December 15, 2003 8:07 AM To: [EMAIL PROTECTED] Subject: [Nant-users] Problem with solution task Hi I am using nant-0.8.2 stable release to build a number of VB.Net projects (using the <solution> task for the actual build). Everything seems to work fine except for the last project in the set. Nant reports success but the built executable (winexe) appears to have a memory exception (Application Error - The instruction at "0x8524da6e" referenced memory at "0x8534da6e". The memory could not be "read".). When I build the executable with VS it works fine. I have tried referencing both the .sln and .vbproj files in my <solution> task with the same result. Any views or statements expressed in this message are those of the individual sender, and Sanlam accepts no liability therefore, except where the sender specifically states them to be those of Sanlam. Enige sienswyses of stellings wat in hierdie boodskap uitgedruk word, is dié van die individuele afsender, en Sanlam aanvaar geen aanspreeklikheid daarvoor nie, behalwe waar die afsender uitdruklik vermeld dat dit dié van Sanlam is. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
