Front Page Extensions w/ XP Pro

[Webforumz Staff]

I develop ASP using IIS 5.1 on XP Pro. Totally happy, no problems. I decided to reinstall VS.NET so that I can get back into doing some ASP.NET stuff with C#, and the install says it requires Frontpage Server Extensions.

I remember last time I installed the Extensions that it went through every folder on my web server and added all the vti_whatever crap that I totally didn't need on any of my classic ASP project. Maybe I'm picky but I hated filtering all that junk out when uploading my code, so I eventually spent an hour deleting all those folders by hand.

So what I'm wondering is can you install the Extensions on just part of your local site? Say a subfolder I'd use for just the asp.net stuff? I see that there's a "Web Sites" folder in the IIS setup, but it looks like I can only have the one "Default Web Site" in it and I can't see how to add another site. Or do I really need the Extensions in the first place cause while I'm developing on here I'm not going to host the site here in the end?

[Rob]

Hi...

This is less of an issue than you think...

Go ahead and install the extensions. When you want to get rid of unneeded folders, just click start, run, find files and folders.

type _vti into the file box and point the folder box to your web root.

just highlight everything it finds and hit delete.... easy, huh

Also, the reason you can't add a site, is that you are not running a SERVER OS. win 95, win98, win2000 and winxp all support only one website (Default Website)... however install win 2000 server, .NET server 2003 and you can install as many as you like.

I get round this by having each website in a seperate folder under the web root.

[Webforumz Staff]

My development drive has 1,100 folder with 3gb of files so I thought I'd keep looking for another solution. After some messing around I think I found a way around it.

I set the Default website to point to a temporary folder, then installed the FrontPage Server Extensions. It added it's junky folders to the temp folder as usual.

Then I pointed the Default website back to my normal development drive and everything seems to be working fine. I can run all my old ASP stuff as usual and no extra stuff gets added to them, and I can add new .NET web applications and they seem to work fine (at least so far).