System.DirectoryServices & Creatiing Virtual Directorys W2003

[Ken]

Hi,

We have a component that we've used successfully under W2000 to create
virtual directories on an IIS 5.0 web server. We're in the process of
upgrading to W2003 and I'm now encountering an exception when trying to
create the IIS virtual directory.

The component is .net, v 1.14 and is using System.DirectoryServices. The
code that does the work is:

vDir = iisAdmin.Children.Add(virtualDirectory.Name, "IIsWebVirtualDir");
vDir.Properties["AppFriendlyName"][0] = virtualDirectory.AppFriendlyName;
vDir.Properties["AppIsolated"][0] = virtualDirectory.AppIsolated;
vDir.Properties["AccessRead"][0] = virtualDirectory.AccessRead;
vDir.Properties["AccessWrite"][0] = virtualDirectory.AccessWrite;
vDir.Properties["AccessExecute"][0] = virtualDirectory.AccessExecute;
vDir.Properties["AccessScript"][0] = virtualDirectory.AccessScript;
vDir.Properties["AccessSource"][0] = virtualDirectory.AccessSource;

vDir.Properties["AccessNoRemoteRead"][0] =
virtualDirectory.AccessNoRemoteRead;
vDir.Properties["AccessNoRemoteWrite"][0] =
virtualDirectory.AccessNoRemoteWrite;
vDir.Properties["AccessNoRemoteExecute"][0] =
virtualDirectory.AccessNoRemoteExecute;
vDir.Properties["AccessNoRemoteScript"][0] =
virtualDirectory.AccessNoRemoteScript;
vDir.Properties["EnableDefaultDoc"][0] = virtualDirectory.EnableDefaultDoc;
vDir.Properties["EnableDirBrowsing"][0] =
virtualDirectory.EnableDirectoryBrowsing;
vDir.Properties["AccessFlags"][0] = virtualDirectory.ExecutionPermission;
vDir.Properties["DefaultDoc"][0] = virtualDirectory.DefaultDoc;

vDir.Properties["Path"][0] = virtualDirectory.Path;

if(isApplication && virtualDirectory.AppIsolated ==
Wellmark.Enterprise.Utilities.Deployment.Applicati onIsolationType.High)
{
vDir.Invoke("AppCreate", false);
}

vDir.CommitChanges();
vDir = iisAdmin.Children.Add(virtualDirectory.Name, "IIsWebVirtualDir");
vDir.Properties["AppFriendlyName"][0] = virtualDirectory.AppFriendlyName;
vDir.Properties["AppIsolated"][0] = virtualDirectory.AppIsolated;
vDir.Properties["AccessRead"][0] = virtualDirectory.AccessRead;
vDir.Properties["AccessWrite"][0] = virtualDirectory.AccessWrite;
vDir.Properties["AccessExecute"][0] = virtualDirectory.AccessExecute;
vDir.Properties["AccessScript"][0] = virtualDirectory.AccessScript;
vDir.Properties["AccessSource"][0] = virtualDirectory.AccessSource;

vDir.Properties["AccessNoRemoteRead"][0] =
virtualDirectory.AccessNoRemoteRead;
vDir.Properties["AccessNoRemoteWrite"][0] =
virtualDirectory.AccessNoRemoteWrite;
vDir.Properties["AccessNoRemoteExecute"][0] =
virtualDirectory.AccessNoRemoteExecute;
vDir.Properties["AccessNoRemoteScript"][0] =
virtualDirectory.AccessNoRemoteScript;
vDir.Properties["EnableDefaultDoc"][0] =
virtualDirectory.EnableDefaultDoc;
vDir.Properties["EnableDirBrowsing"][0] =
virtualDirectory.EnableDirectoryBrowsing;
vDir.Properties["AccessFlags"][0] =
virtualDirectory.ExecutionPermission;
vDir.Properties["DefaultDoc"][0] = virtualDirectory.DefaultDoc;

vDir.Properties["Path"][0] = virtualDirectory.Path;

if(isApplication && virtualDirectory.AppIsolated ==
Wellmark.Enterprise.Utilities.Deployment.Applicati onIsolationType.High)
{
vDir.Invoke("AppCreate", false);
}

vDir.CommitChanges();
I'd appreciate it if someone can point me to the info that tell's me what's
changed between the iis 5 and iis 6 that would be causing this problem