VS2008 - Front Page Extensions
Good day,
I'm looking for a layman's explanation of the relationship between FrontPage Server Extensions and a .NET web application.
Background: A team of us is using VS2008 to develop a web application that is hosted on a network server. This is an internal project - we are all in the same domain. I created a site on a server and made sure that everyone has sufficient rights to the filesystem on that server. However, when they tried to open the site through VS, they were prompted for a username and password. I don't understand why they are being asked to authenticate - they already had the necessary file system permissions. We know this because they were able to go to the site and create folders / files, delete folders / files, whatever.
After googling I came to the conclusion that I need to add them to the "Author" role in the FrontPage Server Extensions 2002 administration page via VS. After that I did it, everything was fine.
It seems to me that these permissions have nothing to do with the file system permissions on the server, IIS, or website. It seems to me that these permissions are irrelevant, but I am obviously wrong.
I'm looking for a little story about what goes on behind the scenes.
Thank.
Please refer to this link for security issues: http://docs.sun.com/source/816-5666-10/esapmsfp.htm
If you installed the extensions after you configured the permissions, you may have to replace the ACLs on those files by resetting the project folder permissions due to the vti * folders and files it creates in the web application itself; it resets the permissions on these folders and removes the set permissions. Also, it can map your application's _vti_bin folder to the program's file folder folder. I know the answer is a little late, but better late than never. I always tell her.
Would recommend developing a TFS source control to do development using a UNC common path.