Re: [Nant-users] RE: WebDAV and permissions for solution task

[Matthew Mastracci]

Ahh...   How does VS.NET get the mapping from IIS path to file share?  I 
would love to know.  :)  I've had so many problems with an auto-build 
system when the web share wasn't properly set up, etc. 

From running Etherial traces while opening/compiling an ASP.NET trace, 
I got the impression that it was using FrontPage as the default, 
however.  I would definitely like more information about this part of 
the process!

Thanks,
Matt
Bernard Vander Beken wrote:

Hello Matthew,

While it is true that VS.NET can use FrontPage extensions to do this,
another way is to use file shares. This access mode tends to be faster
and (obviously) does not require to have FrontPage extensions installed.
This is an option when creating a new project, and can be checked in the
Project Properties at 
Common Properties > Web Settings > Web Access Mode.

Best regards,

Bernard

-----Original Message-----
From: Matthew Mastracci [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 09, 2003 5:06 PM
To: [EMAIL PROTECTED]; Williams, Kevin
Subject: [Nant-users] RE: WebDAV and permissions for solution task

[EMAIL PROTECTED] wrote:

 

Matt,

Thank you for your reply. Unfortunately, I'm even more confused now.
   

The
 

.sln file points to http://localhost/blah/blah.csproj yet VS.NET is
   

able to
 

resolve all this and compile just fine, without any extra steps to
   

enable
 

WebDAV write access and source access.

There is a build tool from Microsoft SDC available at
http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=
   

2cb20
 

e79-d706-4706-9ea0-26188257ee7d which has a solution task. Their task
   

calls
 

"devenv.exe" and passes the build configuration and solution file path
   

as
 

command line arguments. I assume Nant doesn't wish to impose the
   

dependency
 

of VS.NET being installed, but if we're talking about parsing a .sln
   

file,
 

where would one come from if not generated by VS.NET?

I don't mean to second guess whomever wrote the solution task for Nant,
   

but
 

extra steps to configure WebDAV access doesn't seem practical.

Kevin

   

I'm actually the original author of this task.  I don't mind 
suggestions.  :)  The goal of this task is to allow compiling of 
.sln/.csproj files without a copy of VS.NET (ie: an extra license).

VS.NET uses frontpage extensions to update the project.  If someone can 
find me documentation for these, I could implement them.  They don't 
require any setup on the server side and they ignore the 
read/write/script source access permissions on the web project.  It 
makes me wonder how secure an ASP.NET project is, however.  I had 
originally implemented WebDAV, as a quick way to get a solution 
compiling.  In retrospect, I think I should have looked at other options

first.

The best solution is for us to create a URL->physical path mapping in 
the <solution> task to handle these projects.  I just haven't had the 
time to do this, however.

BTW, you can always call devenv.exe yourself, using the <exec> task.

Matt.



-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
 





-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users