Question about TARGETSITE property of web setup

[=?Utf-8?B?TmFkYXYgUG9wcGxld2VsbA==?=]

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

[Steven Cheng[MSFT]]

Hi Nadav,

As for the Visual Studio setup project, so far its default interface only
provide selecting different site from local IIS server. Therefore, the
TARGETSITE string may only vary on the site number/ID part(e.g.
/LM/W3SVC/1 /LM/W3SVC/XXXXX ). The "/LM" here just represent the
localhost, so I think you can freely remove it to construct the metabase
path for the aspnet_regiis tool.

BTW, for those properties in setup project, I've posted some information in
your another thread " Is there a list of all standard setup project
properties".

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[=?Utf-8?B?TmFkYXYgUG9wcGxld2VsbA==?=]

Hi Steven,

Thanks for your quick reply,

Nadav

"Steven Cheng[MSFT]" wrote:

Hi Nadav,

As for the Visual Studio setup project, so far its default interface only
provide selecting different site from local IIS server. Therefore, the
TARGETSITE string may only vary on the site number/ID part(e.g.
/LM/W3SVC/1 /LM/W3SVC/XXXXX ). The "/LM" here just represent the
localhost, so I think you can freely remove it to construct the metabase
path for the aspnet_regiis tool.

BTW, for those properties in setup project, I've posted some information in
your another thread " Is there a list of all standard setup project
properties".

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.