This post originated from an RSS feed registered with .NET Buzz
by David Cumps.
Original Post: FrontPage Server Extensions - IIS Metabase
Feed Title: David Cumps
Feed URL: http://weblogs.asp.net/cumpsd/rss?containerid=12
Feed Description: A Student .Net Blog :p
This says 'Setting FrontPageWeb to true causes FrontPage Manager to create the files required for FrontPage Server Extensions. Setting FrontPageWeb to false causes these files to be deleted.'.
Everything seems allright, just like every other property I set this to true and except it to work. Like this:
1// First we get the AD object representing our webserver
2DirectoryEntry iisServerRoot = new DirectoryEntry("IIS://localhost/W3SVC");
3 4// We create a new site on the specified siteId
5DirectoryEntry deNewWwwSite = (DirectoryEntry)iisServerRoot.Invoke("Create", "IIsWebServer", 10);
6 7// Takes care of FrontPage Manager providing files for FrontPage Extensions
8deNewWwwSite.Properties["FrontPageWeb"][0] = true;
9 10deNewWwwSite.Invoke("SetInfo");
11deNewWwwSite.CommitChanges();
12 13deNewWwwSite.Close();
14deNewWwwSite.Dispose();
(Most stuff left out)
Well, it didn't work. In IIS it would still say FrontPage Extensions were not present, and the directories didn't get made.
I looked everywhere to find something else involving FrontPage, without any luck.
But then I found this KB article (300543). And althou it's talking about IIS 4.0, 5.0 and 5.1, it does work on IIS 6.0 as well.
So here you go, to install FrontPage Extensions you have to run: "C:\Program Files\Common Files\Microsoft Shared\web server extensions\50\bin\owsadm.exe" -o install -p /LM/W3SVC/SITEID -u USERNAME -sp publish
And to uninstall them: "C:\Program Files\Common Files\Microsoft Shared\web server extensions\50\bin\owsadm.exe" -o fulluninstall -p /LM/W3SVC/SITEID -u USERNAME
Previous Topic
