qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John O'Hara" <john.r.oh...@gmail.com>
Subject Re: .NET Client builds
Date Fri, 11 May 2007 08:39:32 GMT
A totally good idea.
The build system should be independent of any particular IDE.

We've found that using ANT for Java and never IDE project files is a really
Good Thing.

John

On 11/05/07, Tomas Restrepo <tomas.restrepo@devdeo.com> wrote:
>
> One of the targets for the .NET client (at least for the majority of the
> functionality) is currently Mono, which I think is a good idea. However,
> keeping the build is a bit of a chore currently.
>
> Right now we have, in theory, MonoDevelop project files for the solution.
> However, the truth is these haven't been updated in a long while and
> maintaining them both *and* the VS solution files is quite inconvenient.
> And
> for the .NET 1.1 build, currently MSBee is needed.
>
> I'd like to propose a few changes here to simplify this:
>
> 1- Get rid of the MonoDevelop project files. Currently, there's no one
> that
> is doing development on the .NET client on mono.
>
> 2- Create a global NAnt build file instead that can be used to generate
> releases for all three platforms (.NET v1.1 and v2.0 and mono). Since we
> don't change projects very often, keeping this one in sync will be far
> easier than dealing with the MonoDevelop project files, so we'll rarely
> need
> to modify it. We'd still use the VS project files for regular development
> and builds, though.
>
> Any comments?
>
> Tomas Restrepo
> http://www.winterdom.com/weblog/
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message