visual studio .net ide:
Hi Nadav,
Thank you posting!
[quoted text, click to view] >1. when installing the MSI on a computer that has both
>dotnet 1.1 & 2.0 installed with the root of the web service
>registered to use dotnet 1.1 scriptmaps the setup will
>NOT register the created virtual directory to use
>dotnet 2.0.
yes, the VS2005's setup project doesn't provide the function to set the
asp.net version of an installing virtual directory. You need to configure
that vdir's setting manually via the IIS manager.(The target vdir's
properties | ASP.NET tab | ASP.NET version).
Another way to configure this setting is to use an IIS Registration tool
that ships with the corresponding .NET Framework--aspnet_regiis. You can
use the "-s" option with the target vdir's path to achieve this. That tool
is located in the your's system's
..\WINDOWS\Microsoft.NET\Framework\v2.0.50727 directory. I suggest you
refer to the following MSDN article for the details:
Configuring an ASP.NET Application for an ASP.NET Version
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
l/cpconconfiguringaspnetapplicationforaspnetversion.asp
[quoted text, click to view] >2. when uninstalling the MSI the folder is removed from the file system,
but
>the virtual directory is NOT remove from IIS.
I am afraid this behavior is also by design, the installation program's
uninstallation procedure will clean the stuff which it installed before,
but it will not remove that virtual directory from the web server. You can
remove that virtual directory manually in the IIS manager or via a script.
Thanks!
Best regards,
Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.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/subscriptions/support/default.aspx. ==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.