G
Guest
Hi everybody,
I'm writing a custom action for a web setup to register my web site to use
dotnet2.0.
Everything works OK, there only one thing I'm not sure of.
The parameters that I pass from the websetup to my custom application are
TARGETVDIR="XmlAPI"
TARGETSITE="/LM/W3SVC/1"
However the path I need to pass to aspnet_regiis is "/W3SVC/1/ROOT/XmlAPI".
Right now what I'm doing is removing the "/LM" and adding "/ROOT/" between
the site and the vdir.
What I want to know is will this always work or are there some cases where
this will not give me the right path for aspnet_regiis.
Thanks
Nadav
I'm writing a custom action for a web setup to register my web site to use
dotnet2.0.
Everything works OK, there only one thing I'm not sure of.
The parameters that I pass from the websetup to my custom application are
TARGETVDIR="XmlAPI"
TARGETSITE="/LM/W3SVC/1"
However the path I need to pass to aspnet_regiis is "/W3SVC/1/ROOT/XmlAPI".
Right now what I'm doing is removing the "/LM" and adding "/ROOT/" between
the site and the vdir.
What I want to know is will this always work or are there some cases where
this will not give me the right path for aspnet_regiis.
Thanks
Nadav