On 08/15/2011 11:26 AM, Stefan Bodewig wrote: > Like I said later, I'm not convinced we need to target 4.0 at all as the > 2.0 version should just work. For client profile we could use a > stripped down 2.0 version or explicitly target 3.5 (client profile). > But I may very well be missing some nuance.
You once asked if VS2010 can change the target profile. Yes, it can. I did it at work some time. But unfortunatly it is something that defines a projects dependencies. So it is not something that can simply be changed by a built tool. In VS2010 you have to configure the project to be targeted for a specific .NET framework and VS makes sure the project finds the correct libraries. > We don't have any (working) CI for log4net right now. The only one I'm > aware of is Gump and this one only builds the Mono parts so isn't really > useful. It doesn't perform any tests either. *ouch* Now that you say it. I just ran nant from my ubuntu laptop and was impressed that it went through without complains. :-) I just built log4net for mono 1.0 and 2.0. *laughing* I'm going to copy that dll to my windows pc and see if I can use it across different projects (2.0, 3.0, 3.5, 4.0, 3.5CP, 4.0CP) and report the results. > Jenkins - one option available from ci.apache.org - does support MSBuild > (on Windows, of course) and likely NAnt as well. I know the Lucene.NET > project is looking for CI builds so the infrstructure for "real" .NET > builds should be there at one point. Where did you read up jenkins? There's continuum and buildbot. The latter runs on a win7 machine and therefore could be able to run msbuild. Btw, why does the nant build only produce mono files? -- Dominik Psenner ## OpenPGP Key Signature ################################# # Key ID: B469318C # # Fingerprint: 558641995F7EC2D251354C3A49C7E3D1B469318C # ##########################################################
signature.asc
Description: OpenPGP digital signature
