> -----Original Message-----
> From: Ian MacLean [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 19 January 2005 11:35 AM
> To: Angus Grant
> Cc: nant-users@lists.sourceforge.net
> Subject: Re: [Nant-users] .NET SDK Requirements
> 
> Angus Grant wrote:
> 
> > I am fairly sure the .NET framework does not include 
> vb.net, c#, etc 
> > compilers, resource file compilers, etc, etc. You need to 
> install the 
> > framework sdk to get these.
> >
> half right. It includes vbc.exe, csc.exe but not the resource 
> compilers.
> 
> > I wouldn't have thought you would need the .Net framework on 
> > production servers unless you are running ASP.NET application.
> 
> you have it backwards. csc.exe comes with the framework for precisely 
> that reason - so that ASP.NET can work.

oh yeh, of course. forgot about the "compile on first load" feature.

well maybe my half-correct answer helped you with the correct answer. please 
say it was so. :-) global embarrassment is such a downer!
 
> > There shouldn't really be any reason for having .NET sdk on 
> production 
> > servers. Maybe you should look at a build server which then copies 
> > compiled binaries across to your QA, UAT, and production 
> servers, etc. 
> > Or modify your build scripts to have targets for copying 
> files across 
> > to various servers.
> >
> NAnt used to run without the SDK installed - it would just 
> fail if you 
> tried to run somthing like <resgen> - ie somthing that 
> requires the SDK 
> - maybe thats changed recently.
> Aah - I see that you are using <vbc> with its <resources> 
> child element 
> - thats probably the problem.
> 
> Ian
<SNIP>


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to