[MonoDevelop] Mono 2.8 .Net 4.0 and Nunit

[Matt Calder]

Dale,

That worked, thanks.

Matt

On Fri, Oct 22, 2010 at 11:05 AM, Dale Ragan <dale.ragan at sinesignal.com> wrote:
> You will need to do two things:
>
> 1.  When running nunit-console, you will need to pass -framework flag and
> set it to mono-4.0
>
> 2.  Modify nunit-console.exe.config by adding under the <configuration>
> section:
>  <startup>
>    <requiredRuntime version="v4.0.####" /> ### = released version of the
> .net 4.0 runtime.  I'm not sure what it is off the top of my head
>  </startup>
>
>  and adding under <configuration><runtime>
>
>  <legacyUnhandledExceptionPolicy enabled="1" />
>  <loadFromRemoteSources enabled="true" />
>
> HTH,
>
> Dale
>
>> Dale,
>>
>> Thanks for the quick reply. In fact in my effort to diagnose the
>> problem I had grabbed the latest nunit and tried to run my tests in
>> that. However, that gives an error (copied below). It seems to be
>> unable to locate "mono-4.0.30319 framework". I apologize if I am
>> missing something obvious, any help is greatly appreciated. And, yes,
>> I'd be more than happy to help test out a new version.
>>
>> Matt
>>
>> NUnit version 2.5.7.10213
>> Copyright (C) 2002-2009 Charlie Poole.
>> Copyright (C) 2002-2004 James W. Newkirk, Michael C. Two, Alexei A.
>> Vorontsov.
>> Copyright (C) 2000-2002 Philip Craig.
>> All Rights Reserved.
>>
>> Runtime Environment -
>>    OS Version: Unix 2.6.32.25
>>   CLR Version: 2.0.50727.1433 ( 2.8 (tarball Tue Oct 19 10:17:33 EDT 2010)
>> )
>>
>> ProcessModel: Default    DomainUsage: Single
>> Execution Runtime: Default
>> Unhandled Exception:
>> System.ArgumentException: The mono-4.0.30319 framework is not available
>> Parameter name: framework
>>   at NUnit.Util.TestAgency.GetAgent (NUnit.Core.RuntimeFramework
>> framework, Int32 waitTime, Boolean enableDebug) [0x00000] in <filename
>> unknown>:0
>>   at (wrapper remoting-invoke-with-check)
>> NUnit.Util.TestAgency:GetAgent (NUnit.Core.RuntimeFramework,int,bool)
>>   at NUnit.Util.ProcessRunner.Load (NUnit.Core.TestPackage package)
>> [0x00000] in <filename unknown>:0
>>   at NUnit.ConsoleRunner.ConsoleUi.Execute
>> (NUnit.ConsoleRunner.ConsoleOptions options) [0x00000] in <filename
>> unknown>:0
>>   at NUnit.ConsoleRunner.Runner.Main (System.String[] args) [0x00000]
>> in <filename unknown>:0
>>
>>
>>
>>
>> On Fri, Oct 22, 2010 at 10:09 AM, Dale Ragan <dale.ragan at sinesignal.com>
>> wrote:
>>> This is on my TODO for MonoDevelop 2.6.  Waiting on some internal
>>> decisions to be made before I start on it, but it is on the radar.  For
>>> now, the only option is to run the unit-tests externally with the 2.5.3
>>> or
>>> above verson of nunit-console.  Keep an eye on the MonoDevelop's git
>>> repository or this mailing list for when it's introduced and you can
>>> help
>>> test the functionality.
>>>
>>> - Dale
>>>
>>>> All,
>>>>
>>>> I recently upgraded to Mono 2.8. Subsequently, I started converting
>>>> projects to use .Net 4.0. This has caused all my Nunit tests to fail.
>>>> The Nunit site says that one needs Nunit 2.5.6 or better to run in
>>>> .Net 4.0 in Mono. It appears Monodevelop is running it's own copy of
>>>> Nunit, and that appears to be 2.4.8 (or possible 2.4.7). Is it
>>>> possible to change that? And if so, how would one change that?
>>>>
>>>> It did not appear to be sufficient to run tests under Nunit
>>>> externally, that would be less than ideal, but would be better than no
>>>> tests at all.
>>>>
>>>> Thanks for any help,
>>>>
>>>> Matt
>>>> _______________________________________________
>>>> Monodevelop-list mailing list
>>>> Monodevelop-list at lists.ximian.com
>>>> http://lists.ximian.com/mailman/listinfo/monodevelop-list
>>>>
>>>
>>>
>>>
>> _______________________________________________
>> Monodevelop-list mailing list
>> Monodevelop-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/monodevelop-list
>>
>
>
>