Re: targeting 2.0, 4.0 and Mono runtimes

>
>
> Also, NUnit is building for .net 1, 2, 3.5 and mono 1 and 2 with NAnt.
> Maybe not the most easily maintainable solution as you have to set up a
> parallel build process to MSBuild but it's proven to work quite well.
>
> On Sun, May 1, 2011 at 23:48, Sebastien Lambla <seb@...> wrote:
>
>>
>>
>> Be ready for very ugly scripts that you’ll have to maintain manually **a
>> lot**. This stuff gets nasty real quick.
>>
>>
>>
>> *From:* altdotnet@... [mailto:altdotnet@...] *On
>> Behalf Of *Simone Busoli
>> *Sent:* 01 May 2011 22:39
>>
>> *To:* altdotnet@...
>> *Subject:* Re: [altdotnet] targeting 2.0, 4.0 and Mono runtimes
>>
>>
>>
>>
>>
>> I think you can more or less do the same with bare msbuild:
>> http://msdn.microsoft.com/en-us/library/bb397456.aspx
>>
>> On Sun, May 1, 2011 at 23:21, Sebastien Lambla <seb@...> wrote:
>>
>>
>>
>> An openwrap one. We automate the calling of msbuild to enable retargeting
>> dynamically your build so you can generate packages for multiple versions of
>> .net in one go.
>>
>>
>>
>> *From:* altdotnet@... [mailto:altdotnet@...] *On
>> Behalf Of *Dotan N.
>> *Sent:* 01 May 2011 21:36
>>
>>
>> *To:* altdotnet@...
>> *Subject:* Re: [altdotnet] targeting 2.0, 4.0 and Mono runtimes
>>
>>
>>
>>
>>
>> Thanks Seb, didn't know about that one.
>>
>> is 'profile' an msbuild or openwrap concept?
>>
>> On Sun, May 1, 2011 at 11:20 PM, Sebastien Lambla <seb@...>
>> wrote:
>>
>>
>>
>> If you use openwrap, it’s as simple as
>>
>>
>>
>> build: msbuild; profile=net20;profile=net40
>>
>>
>>
>>
>>
>>
>>
>> *From:* altdotnet@... [mailto:altdotnet@...] *On
>> Behalf Of *Dotan N.
>> *Sent:* 01 May 2011 20:54
>> *To:* altdotnet@...
>> *Subject:* Re: [altdotnet] targeting 2.0, 4.0 and Mono runtimes
>>
>>
>>
>>
>>
>> Thanks Greg,
>>
>> If I build my binaries to be on the .net 4.0 runtime someone with only a
>> 2.0 runtime wouldn't be able to run it.
>>
>> If I choose the lowest common denominator i would use strictly the 2.0
>> runtime but i'd like to fade that off gradually.
>> Thats the kind of dilemma i'm facing
>>
>>
>>
>>
>>
>> On Sun, May 1, 2011 at 5:11 PM, Greg Young <gregoryyoung1@...>
>> wrote:
>>
>>
>>
>> If your code already works with 2.0 and doesny use anything not available
>> in mono your dll should already work in all 3 no need to targey specifically
>>
>> On 1 May 2011 14:32, "Dotan N." <dipidi@...> wrote:
>> > Hi All,
>> > I'm wondering if anyone can point me to a resource regarding building a
>> > project for .net 2.0 , 4.0 runtimes in a single build as well as for
>> Mono.
>> > I guess what i'm looking for is a structured way to create such a build
>> > without me as the developer having any friction of the technicalities
>> > (IFDEFs etc),
>> > assuming that my code is basic and common to all runtimes.
>> >
>> >
>> > Any suggestions from people who already done such a thing?
>> >
>> > Thanks
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>  
>