Problems Occur When You Connect to Commerce Server with Visual InterDev by Using the FrontPage Server Extensions (277357)

SYMPTOMS

You may experience problems when you connect to a Commerce Server application with Microsoft Visual InterDev by using the FrontPage Server Extensions. These problems appear if the Web site that was originally packaged had the FrontPage Server Extensions enabled.

The Web site that you unpackage appears as though the FrontPage Server Extensions are already installed. However, when you connect with Visual Interdev, the site is unavailable in the drop-down list for the existing FrontPage enabled applications.

CAUSE

The Commerce Server Site Packager packages all files and subdirectories under the physical root of the Virtual Directory. This includes all of the _vti directories that are not moved by applications that are FrontPage aware.

WORKAROUND

To work around this behavior, do one of the following:

Delete the _vti directories on the source before you package the site.

-or-
After you unpackage the Commerce Server site, manually delete the physical _vti folders, and then turn on the FrontPage Server Extensions again. To do this, right-click the application in the Internet Information Service (IIS) snap-in, click All Tasks, and then click Configure Server Extensions.

-or-
After you unpackage the Commerce Server site, right-click the application, click All Tasks, click Convert Server Extensions Web to Directory, and then turn on the FrontPage Server Extensions again. To do this, right-click the application in the IIS snap-in, click All Tasks, and then click Configure Server Extensions.

STATUS

This behavior is by design in the current implementation of the Commerce Server Site Packager. The Cabarc.exe file does not exclude certain directories when you package a Commerce Server site.