Bug 209 - Unable to run Nant script on Mono 2.10.3
Summary: Unable to run Nant script on Mono 2.10.3
Status: VERIFIED FIXED
Alias: None
Product: Compilers
Classification: Mono
Component: VisualBasic ()
Version: unspecified
Hardware: PC Mac OS
: --- critical
Target Milestone: ---
Assignee: Rolf Bjarne Kvinge [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2011-08-05 18:45 UTC by Prashanth Kamath
Modified: 2011-08-24 01:13 UTC (History)
2 users (show)

Tags: Nant
Is this bug a regression?: ---
Last known good build:


Attachments
Crash report on Mac (11.56 KB, application/octet-stream)
2011-08-05 18:45 UTC, Prashanth Kamath
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
VERIFIED FIXED

Description Prashanth Kamath 2011-08-05 18:45:54 UTC
Created attachment 75 [details]
Crash report on Mac

I was using /usr/bin/nant with mono 2.10.2 and monobjc 2.0.505. It was working fine till I upgraded to Mono 2.10.3. Now I am getting an exception while using nant. I have attached the crash report. The OS is Mac 10.6.4
Comment 1 Miguel de Icaza [MSFT] 2011-08-09 10:16:47 UTC
Can you provide a test case that we can use to reproduce?
Comment 2 Prashanth Kamath 2011-08-24 01:13:27 UTC
This has been fixed in 2.10.4. Hence this can be closed.