Yes. I am using it on my integration box. What im working on right now
is a tool to allow users to select an arbitrary fileset from my
subversion repository, push those files into the QA local repository,
and do an on demand compile. While I could probably hack CC.Net to do
something like that, it seemed much simpler to just write a tool to do
so. I have the subversion part working, but Nant is giving me issues.

Peter

> -----Original Message-----
> From: Marc Holmes [mailto:[EMAIL PROTECTED] 
> Sent: Friday, April 01, 2005 10:33 AM
> To: Peter A. Pociask; nant-users@lists.sourceforge.net
> Subject: RE: [Nant-users] Triggering Nant Build from ASP.Net Web Page
> 
> Have you had a look at CruiseControl.Net 
> (http://ccnet.thoughtworks.com)?
> It will do what you need and a lot more besides.
> Alternatively you could roll your own remoting wrapper.
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Peter A.
> Pociask
> Sent: 01 April 2005 16:25
> To: nant-users@lists.sourceforge.net
> Subject: [Nant-users] Triggering Nant Build from ASP.Net Web Page
> 
> 
> I am trying to call nant from an asp.net (vb.net) web 
> application. I am using the following code:
> 
>     Public Function compile(ByVal compileArg) As String
> 
>         Dim args As String
>         args += " -f:" &
> ConfigurationSettings.AppSettings("nantBuildFile")
>         args += " " & compileArg
> 
>         'Response.Write(args)
>         Dim proc As New System.Diagnostics.Process
>         proc.StartInfo.WorkingDirectory = "d:\"
>         proc.StartInfo.RedirectStandardOutput = True
>         proc.StartInfo.RedirectStandardError = True
>         proc.StartInfo.FileName =
> ConfigurationSettings.AppSettings("nantBin") & "nant.exe"
>         proc.StartInfo.Arguments = args
>         proc.StartInfo.UseShellExecute = False
>         proc.Start()
> 
>         'Response.Write("Output " & proc.StandardError.ReadToEnd &
> "<BR>")
>         Dim out = proc.StandardOutput.ReadToEnd
> 
>         proc.WaitForExit()
>         proc.Dispose()
> 
>         Return out
>     End Function
> 
> I am attempting to execute a build script that works fine 
> when invoked from the command line, but it fails miserably 
> when called from the web page. It returns a bunch of lines 
> that look like the following:
> 
>  [delete] Deleting file FILE.
>   [foreach] D:\ServerConf\default.build(32,6):
>   [foreach] Cannot delete file FILE
>   [foreach]     Invalid File or Directory attributes value.
> 
> I am almost certain it is some sort of permissions issue, but 
> I'm not sure what nant needs to run in terms of environment 
> variables and temp space. Has anyone attempted this, and if 
> so, could you give me some guidance? 
> 
> 
> Peter Pociask
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by Demarc:
> A global provider of Threat Management Solutions.
> Download our HomeAdmin security software for free today!
> http://www.demarc.com/Info/Sentarus/hamr30
> _______________________________________________
> Nant-users mailing list
> Nant-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nant-users
> This e-mail (and any attachments) is confidential and may 
> contain personal views which are not the views of the BBC 
> unless specifically stated.
> If you have received it in error, please delete it from your 
> system. Do not use, copy or disclose the information in any 
> way nor act in reliance on it and notify the sender 
> immediately. Please note that the BBC monitors e-mails sent 
> or received.
> Further communication will signify your consent to this.
> 


-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to