Can someone tell me what is the advantage of using Nant to build the assemblies rather than using the
devenv.com using the he solution file.
I can see that it is helpful if one does not have Visual Studio.NET. But are there any other advantages.
Any information will be helpful because We are trying to figure out the best way to build the assemblies.
Thanks,
Kishore
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 9:28 AM
To: Scott Hernandez
Cc: [EMAIL PROTECTED]
Subject: Re: [Nant-users] Support for .NET Compact Framework
Hi Scott,
Right now, the CFResGen has the same functionality and the same commandline options. The only difference between the ResGen and CFResgen, is the name of the executable to use and the path to that executable. So I don't think it's a good idea to create a separate task, I think the current task should be refactored to support both the .NET Compact Framework and the full .NET Framework. In fact I guess all .NET tasks should be able to behave differently based on the target platform (.NET 1.0, .NET 1.1, .NET CF, Mono, .....).
Thanks,
Gert
"Scott Hernandez"
<[EMAIL PROTECTED]>
To
04/02/03 18:02 <[EMAIL PROTECTED]>
cc
<[EMAIL PROTECTED]>
Subject
Re: [Nant-users] Support for .NET
Compact Framework
Hi Gert,
It seems like issue #4 is the only that cannot be resolved without code changes. As for #1 and #2 you can just use an <arg> inside of the task. For #3 we should really get a specific task for it, but in the mean time you should be able to use the exec task. If you would like to help, you could supply a CFResgen task implementation.
I will address the issue of #4 soon because it affects the all versions of the framework compilers and tools. It also creates issues, as Ian said in an earlier email, with the 1.0 and 1.1 framework tools and compilers. I hope to get to this patched later this week. We will probably need to support a config file and maybe even a config task. I'm not sure whether you would want to specify the target framework via a external config file, or via information in your build file. What do you think?
Please send along any other issues you come across. This is good information as I'm not sure if anyone on the NAnt team is working with the Compact Framework.
Thanks,
Scott
>
> Hi,
>
> Is support for compiling .NET Compact Framework applications (using
> the .NET Framework 1.1 compilers) planned for NAnt ?
>
> In order to support compiling applications for the .NET Compact
> Framework the following changes should be implemented :
>
> - the C# compiler task should support the /nostdlib[+|-] option
> - the VB.NET compiler task should support the /netcf option
> - add support for CFResgen.exe (the resource compiler for the .NET CF)
> to the ResGen task
> - the ProgramFilePath (in MsftFXSDKExternalProgramBase) should return
> the path to the .NET Compact Framework instead of the .NET Framework
> when you're compiling for the .NET CF.
> - ....
>
> Any idea if and when such support will be provided ? I'd be glad to
> help.
>
> Thanks,
>
> Gert
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________
Nant-users mailing list
[EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
