New Post: VDir - putting it under non "Default Web Site"

Still totally stuck.

I deleted, created, deleted, reran MSI same issue.

I did the following:
appcmd list site c:\test\sites.txt
appcmd list vdir c:\test\vdirs.txt
appcmd list app c:\test\apps.txt
I inspected all files, and my desired name "eSecuritelIn" is not there.

This is what the client test app calls: https://somedomain.com:9443/eSecuritelIn/myservice.svc.

I created a small MSBuild file to repro the problem without having to deploy, undeploy repeatedly:

<Project DefaultTargets="DeployVirtualDirectory"

xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

<Import Project="c:\Program Files (x86)\MSBuild\DeploymentFrameworkForBizTalk\5.0\Microsoft.Sdc.Common.tasks"/>
<UsingTask AssemblyFile="c:\Program Files (x86)\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.Tasks.dll" TaskName="CreateVirtualDirectory" />

<PropertyGroup>
   <IISMetabasePath>IIS://localhost/w3svc/4/Root</IISMetabasePath>
   <Vdir>eSecuritelIn</Vdir>
   <Physdir>e:\Source\neal.walters\DefaultCollection\B2BTeamProject01-SCRUM\Dev\eSecuritel\eSecuritel_In\IISVirtualDir</Physdir>
</PropertyGroup>    

<Target Name="DeployVirtualDirectory">

<CreateVirtualDirectory MetabasePath="$(IISMetabasePath)" Name="$(Vdir)" Path="$(Physdir)" />

</Target>
</Project>

When I run MSBUILD against above file, I get error if I specify <Vdir>eSecuritelIn</Vdir>, but almost any other values works fine.

I manually removed these items from that file, restarted IIS, reran the test MSBUILD, and same issue.

So it exists somewhere, but I have no idea where else to look.

I searched c:\windows\System32\inetsrv\config for the string 'eSecuritelIn' and kept seeing the ApplicationHost.congfig file.
But then a very mysterious thing. If I ran lister, a tool to browse the file, I would see those bytes still in the file. But if I opened the file with NotePad++, those bytes were not there. So I decided to reboot... No good.

Then I read warning in the file: The <customMetadata> section is used internally by the Admin Base Objects (ABO) Compatibility component. Please do not modify its content. So I guess I need to find out how to use ABO now to delete these items?

Neal