Gert Driesen wrote:
>  
>> rom: [EMAIL PROTECTED] 
>> [mailto:[EMAIL PROTECTED] On 
>> Behalf Of Martin Aliger
>> Hello,
>>
>> agreed - 1.0 soon is a good thing. I see only one big thing 
>> which we should
>> addess in 1.0: VS2005 projects. Or MSBuild cooperation. The 
>> same thing.
>>
>> Since many developers are migrating (or already using) 
>> framework 2.0 in
>> VS2005 and we (currently) do not provide direct tools for 
>> projects it uses,
>> they could either: use plain msbuild (deserters!) or use core
>> tasks-csc,regasm etc (and maintain both .csproj and .build) 
>> or (as most of
>> them do today) <exec> msbuild.exe to their .csproj file (and 
>> give up project
>> dependancy resolution and other <solution> features)
>>     
>
> Are people really waiting for this ?
>
> Shouldn't we focus on improving NAnt ?
>   
Supporting VS 2005 one way or another is improving NAnt.
>> As I see it, we could:
>> 1/ state, that new project files used on VS2005 are unsupported
>> 2/ write new task which handles it somehow (aka <msbuild-solution> or
>> <new-vs2005-solution>)
>> 3/ merge required code into current <solution> task
>>     
>
> We already have an <msbuild> task in NAntContrib.
>   
I think we should just move <msbuild> into the main kit.  Quick and easy.

As with versions and version numbers, this sort of packaging decision is 
largely marketing driven.  It belongs there not because of any abstract 
standard concerning what is core and what is optional, but rather 
because having msbuild work out of the box is a requirement to get 
people to use it.
>> Maybe 2 distributions: 1.0 compatible, and 2.0, compiled for 
>> 2.0 and with
>> additional features?
>>     
> This might create too much confusion for (some) users, no ?
>   
I agree.  I suppose it could be hidden by an installation kit, but 
installations are a royal pain.  On the other hand, is it really 
necessary to continue to run under 1.1?  I realize it must continue to 
allow 1.1 as a target, but I thought that it can still do that as a 2.0 
exe.  I don't know how that affects Mono.  (I'm not at all sure that 
there's any requirement for 1.0; I thought that got tossed away 
relatively quickly.)

Are there any problems with requiring .Net 2.0?  There's enough value in 
it that we ought to encourage people to upgrade.  (But maybe I'm biased 
because we're exploiting the new stream encryption features - and I'm 
big on security features.)

Gary




-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to