Thanks guys. You have all confirmed what I had expected. I'll go with the
build server -> FTP -> production server approach I guess. Overall it's
probably a good idea to do it that way anyway.
Thanks again,
Leo
-----Original Message-----
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Tue 1/18/2005 8:35 PM
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.
> 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
>
> -----Original Message-----
> *From:* [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of
> *Hart, Leo
> *Sent:* Wednesday, 19 January 2005 7:18 AM
> *To:* nant-users@lists.sourceforge.net
> *Subject:* [Nant-users] .NET SDK Requirements
>
> Hello,
>
> I'm trying to install and run NAnt on our various QA, UAT and PRD
> servers and have come across a problem that I did not have on my
> local machine. When I run NAnt on my build script locally it
> works fine. When I run it on one of the server machines I get
the
> following error:
>
>
> BUILD FAILED
>
> The SDK for the 'net-1.1' framework is not available or not
> configured.
>
> OK, so obviously this is coming up because neither Visual Studio
> nor the .NET SDK have been installed on the servers. The problem
> is, my company does not permit me to install the .NET SDK on
> production servers, probably with good reason given the security
> hazards it can introduce. It looks like MS does not recommend
> this practice either. Fair enough.
>
> So what is the recommended approach here? I would think given
the
> tasks I am using (I'll lay them out in a little bit), that I'd
> only be required to have the framework installed, but it looks
> like this is not the case. Is there a particular task I am using
> that's pushing this requirement? Maybe I can eliminate it for
now.
>
> Here are the tasks that I'm using:
>
> <property/>
> <if/>
> <ifnot/>
> <mkdir/>
> <vbc><imports/><sources/><resources/><references/></vbc>
> <copy/>
> <foreach/>
>
> If needed, I can include my full build file.
>
> Many thanks in advance...
>
> Leo Hart
>
-------------------------------------------------------
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
<https://access0.fidelity.com/sfshirt,DanaInfo=www.thinkgeek.com+>
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
<https://access0.fidelity.com/lists/listinfo/nant-users,DanaInfo=lists.sourceforge.net,SSL+>
