Hi Neel,
As long as you are OK with having the virtual directory deployment happen during Visual Studio deployments, then leave <IncludeVirtualDirectories>True</IncludeVirtualDirectories> in your .btdfproj but do one of two things:
1) Move <IncludeVirtualDirectories>True</IncludeVirtualDirectories> into the two PropertyGroup's that include Condition="'$(Configuration)' == 'Debug'" and Condition="'$(Configuration)' == 'Release'". Those are used only for Visual Studio deployments and MSI generation, so the property will not be set for server deployments.
OR 2) Change <IncludeVirtualDirectories>True</IncludeVirtualDirectories> to <IncludeVirtualDirectories Condition="'$(IncludeVirtualDirectories)' == ''">True</IncludeVirtualDirectories> which will cause the value to be used only when no value has already been set -- and it will already be set by the install wizard.
Either way is fine, just your preference.
Thanks,
Tom
As long as you are OK with having the virtual directory deployment happen during Visual Studio deployments, then leave <IncludeVirtualDirectories>True</IncludeVirtualDirectories> in your .btdfproj but do one of two things:
1) Move <IncludeVirtualDirectories>True</IncludeVirtualDirectories> into the two PropertyGroup's that include Condition="'$(Configuration)' == 'Debug'" and Condition="'$(Configuration)' == 'Release'". Those are used only for Visual Studio deployments and MSI generation, so the property will not be set for server deployments.
OR 2) Change <IncludeVirtualDirectories>True</IncludeVirtualDirectories> to <IncludeVirtualDirectories Condition="'$(IncludeVirtualDirectories)' == ''">True</IncludeVirtualDirectories> which will cause the value to be used only when no value has already been set -- and it will already be set by the install wizard.
Either way is fine, just your preference.
Thanks,
Tom