Re: [NAnt-users] web projects

[Steve Whitley]

Thank you (both Gert and Bob). I really appreciate the explanitions.  I had thought that the mapping worked the way you explained it (and it is setup as you described w/ the share), but when I put the  actual URL to the server and the share path, nant would complain about not having anything mapped for http://localhost, so I had to change it from its actual url to localhost.  this is what confused me about the whole setup.  our environment is: we develop locally, push to a common dev env. for dev testing, and later on push to a qa server (but thats a manual process).  the visual studio env. is setup to run as the localhost URL that nant is complaining about (when I put the dev server's address in as the url for the webmap). Gert Driesen wrote: -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Steve Whitley Sent: maandag 24 juli 2006 21:25 To: nant-users@lists.sourceforge.net Subject: [NAnt-users] web projects I have a build server that downloads & builds among other things, web projects. those projects are deployed to another computer. in visual studio they have their deploy to web feature that lets you specify a url and the file share path to push the project to the server. I tried specifying the webmap url exactly like I do in visual studio, but it complains I dont have http://localhost/myweb/ mapped to a path... can somebody explain how the web map works. <webmap> allows one to instruct the <solution> task to use local file paths instead of URLs for accessing web project (re)sources, and deploying output files. When these mappings are defined, the <solution> task can process web projects like any other project, instead of having to rely on WEBDAV for reading/writing files. For an example, check out the fifth sample on the <solution> task doc page: http://nant.sourceforge.net/release/0.85-rc4/help/tasks/solution.html Note: Although no longer supported, you can still enable WEBDAV access using the "enablewebdav" attribute on the <solution> task. In that case you don't need do define any mappings, but you might run into (IIS) security/configuration issues. can I use it to deploy the build to the remote server, or do I need the mkiisdir from nant contrib to do this? Even without WEBDAV, you can use it to deploy to a remote server if you can access a (writable) share on that remote server. Eg. If you application is hosted on http://someserver.company.local/MyApplication and that virtual directory corresponds with the directory "c:\inetpub\wwwroot\MyApplication" on that server, then you should share that directory as "MyApplicationDeploy" and configure your <solution> task like this: <solution ....> <webmap> <map url="" class="moz-txt-link-rfc2396E" href="http://someserver.company.local/MyApplication">"http://someserver.company.local/MyApplication" path="\\someserver.company.local\MyApplicationDeploy" /> </webmap> </solution> Hope this helps, Gert

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users