- #INSTALL WEBDAV REDIRECTOR SERVER 2012 HOW TO#
- #INSTALL WEBDAV REDIRECTOR SERVER 2012 SERIES#
- #INSTALL WEBDAV REDIRECTOR SERVER 2012 WINDOWS#
(Incidentally, that's where all of those _vti_nnn folders that FPSE uses come from: the "vti" stands for Vermeer Technologies, Inc.)įrontPage was quickly transitioned into the Microsoft array of Office products, and Microsoft realized that they needed someone to support it. In late 1995, Microsoft bought a little-known Massachusetts-based company named Vermeer Technologies, Inc., which really only had one product: Front.0.
#INSTALL WEBDAV REDIRECTOR SERVER 2012 SERIES#
So before anyone thinks that I fall into the category of people that hate FPSE, in this first part of the series I will explain a brief bit of my history with FPSE.
Over the years I've seen the users of FPSE broken down into two groups: those that love FPSE and those that hate FPSE.
The main goal of this series is to describe some of the highlights and pitfalls that I have run into while transitioning away from FPSE.
#INSTALL WEBDAV REDIRECTOR SERVER 2012 WINDOWS#
Today's blog post will be the first in a series of blog posts that I intend to write about my experiences with putting together a Windows Server 2008 machine without using the FrontPage Server Extensions (FPSE) for any web publishing. If you've already removed FPSE from a web site and you chose the "Uninstall" option, you can remove the _vti_nnn folders from your site by saving the following batch file as "_vti_rmv.cmd" in the root folder of you web site and then running it: In Step 1 of the walkthrough, you would choose "Full Uninstall" as the removal option, and all of your _vti_nnn folders will be deleted. It should be noted, however, that if you are not interested in backwards compatibility, the steps are much simpler. (These metadata settings are all kept in the folders with names like _vti_cnf, _vti_pvt, etc.) The part of that walkthrough that makes backwards compatibility work is where I discuss adding settings for the IIS 7 Request Filtering feature so that FPSE-related metadata files are blocked from normal HTTP requests, but still available to WebDAV. Neither of these tools have native WebDAV support, so you have to map a drive to a WebDAV-enabled web site in order to use those tools, and the instructions in that walkthrough will lead you through the steps to make the FrontPage-related metadata available to those applications over WebDAV. I wrote that walkthrough from the point-of-view that you might want to preserve the FPSE-related metadata in order to open your web site using a tool like Visual Studio or FrontPage.
#INSTALL WEBDAV REDIRECTOR SERVER 2012 HOW TO#
To start things off, I wrote a detailed walkthrough with instructions regarding how to migrate a site that is using FPSE to WebDAV that is located at the following URL: To set the mood for today's blog, let's have a little fun at FPSE's expense.Ī Few Notes about Migrating FPSE Web Sites to WebDAV and Backwards Compatibility That said, I'm quite partial to publishing over HTTP whenever possible, and Windows makes it easy to do because Windows ships with a built-in WebDAV redirector that enables you to map a drive to a web site that is using WebDAV. As the Program Manager for both WebDAV and FTP in IIS I can honestly say that I love both technologies, but I'm understandably biased. Expression Web, FrontPage, Visual Studio, etc. It should be noted, of course, that FTP still works everywhere - e.g. Following up on my last blog post, today's blog post will discuss some of the highlights and pitfalls that I have seen while transitioning from using the FrontPage Server Extensions to publish web sites to WebDAV.
0 kommentar(er)
