> Hello Blasting,
>
> Try to re-register asp.net by calling aspnet_regiis -i for both version
> and check if tab appeared
> BC> I have installed (and un-installed, and reinstalled) framework 2.0
> BC> on a Windows 2003 server.  I still cannot get the property page to
> BC> come up on it.
> BC> BC> When I run aspnet_regiis -lv on the 1.1 framework folder, I get
> BC> this:
> BC>
>>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322>aspnet_regiis -lv
>>> 1.1.4322.0      Valid
>>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\asp
>>> net_isapi.dll
>>> 2.0.50727.0     Valid (Root)
>>> C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\as
>>> pnet_isapi.dll
>>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322>
>>>
> BC> I get identically the same thing when I run that same command from
> BC> the v2.0.50727 folder as well.
> BC> BC> I know that I should get the property page when I have multiple
> BC> versions of .net framework on this computer, but that property page
> BC> is not showing up.
> BC> BC> Is there any way to fix this, to set which framework is going to be
> BC> used on which website (there are multiple websites on this server)?
> BC> BC> Server is running Windows Server 2003, with all service packs &
> BC> updates on it.  It is also running sharepoint services (the small,
> BC> condensed version, not the full-blown Sharepoint).  That appears to
> BC> work, too.
> BC> BC> The 1.1 framework website works, but not the one that is using
> BC> Framework 2.0.
> BC> BC> Any help would be greatly appreciated!!!
> BC> BC> BC
> BC> ---
> WBR,
> Michael  Nemtsev :: blog: http://spaces.msn.com/laflour
>
> "At times one remains faithful to a cause only because its opponents do
> not cease to be insipid." (c) Friedrich Nietzsche
>
>

>> Hello Blasting,
>>
>> Try to re-register asp.net by calling aspnet_regiis -i for both
>> version
>> and check if tab appeared
>> BC> I have installed (and un-installed, and reinstalled) framework
>> 2.0
>> BC> on a Windows 2003 server.  I still cannot get the property page
>> to
>> BC> come up on it.
>> BC> BC> When I run aspnet_regiis -lv on the 1.1 framework folder, I
>> get
>> BC> this:
>> BC>
>>>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322>aspnet_regiis -lv
>>>> 1.1.4322.0      Valid
>>>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\asp
>>>> net_isapi.dll
>>>> 2.0.50727.0     Valid (Root)
>>>> C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\as
>>>> pnet_isapi.dll
>>>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322>
>> BC> I get identically the same thing when I run that same command
>> from
>> BC> the v2.0.50727 folder as well.
>> BC> BC> I know that I should get the property page when I have
>> multiple
>> BC> versions of .net framework on this computer, but that property
>> page
>> BC> is not showing up.
>> BC> BC> Is there any way to fix this, to set which framework is going
>> to be
>> BC> used on which website (there are multiple websites on this
>> server)?
>> BC> BC> Server is running Windows Server 2003, with all service packs
>> &
>> BC> updates on it.  It is also running sharepoint services (the
>> small,
>> BC> condensed version, not the full-blown Sharepoint).  That appears
>> to
>> BC> work, too.
>> BC> BC> The 1.1 framework website works, but not the one that is
>> using
>> BC> Framework 2.0.
>> BC> BC> Any help would be greatly appreciated!!!
>> BC> BC> BC
>> BC> ---
>> WBR,
>> Michael  Nemtsev :: blog: http://spaces.msn.com/laflour
>> "At times one remains faithful to a cause only because its opponents
>> do not cease to be insipid." (c) Friedrich Nietzsche
>>
---
WBR,

> Hello Blasting,
>
> And what about Virtual Folders, not the WebSite? Does virtualFolder have
> such tab?
>
> BC> Michael:
> BC> BC> I ran aspnet_regiis -i under the v1.1.4322 folder, and it gave this
> BC> message:
> BC>
>>> Start installing ASP.NET (1.1.4322.0).
>>> Finished installing ASP.NET (1.1.4322.0).
> BC> I then went to the v2.0.50727 folder and ran aspnet_regiis -i and
> BC> got this message:
> BC> BC> Finished installing ASP.NET (2.0.50727).
> BC> BC> I then did an iisreset to stop & restart IIS.  When I open IIS, and
> BC> then right click on the properties of the website I want to run
> BC> ASP.NET 2.0 for, it shows these tabs:
> BC> BC> Web Site
> BC> Performance
> BC> ISAPI Filters
> BC> Home Directory
> BC> Documents
> BC> Directory Security
> BC> HTTP Headers
> BC> Custom Errors
> BC> but no ASP.NET tab.
> BC> BC> The only difference between the two servers - one where ASP.NET 2.0
> BC> is on and shows the tab, and one where it is not - is that the one
> BC> that doesn't have the tab has Sharepoint Portal Services (the "lite"
> BC> version) on it, which I believe, should not make any difference.
> BC> BC> Other than that - it is the same type & brand of server, with
> BC> similar memory and CPU configuration, both Windows Server 2003, IIS,
> BC> etc.
> BC> BC> Any ideas?
> BC> BC> Michael Nemtsev wrote:
> BC>
>>> Hello Blasting,
>>>
>>> Try to re-register asp.net by calling aspnet_regiis -i for both
>>> version
>>> and check if tab appeared
>>> BC> I have installed (and un-installed, and reinstalled) framework
>>> 2.0
>>> BC> on a Windows 2003 server.  I still cannot get the property page
>>> to
>>> BC> come up on it.
>>> BC> BC> When I run aspnet_regiis -lv on the 1.1 framework folder, I
>>> get
>>> BC> this:
>>> BC>
>>>>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322>aspnet_regiis -lv
>>>>> 1.1.4322.0      Valid
>>>>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\asp
>>>>> net_isapi.dll
>>>>> 2.0.50727.0     Valid (Root)
>>>>> C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\as
>>>>> pnet_isapi.dll
>>>>> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322>
>>> BC> I get identically the same thing when I run that same command
>>> from
>>> BC> the v2.0.50727 folder as well.
>>> BC> BC> I know that I should get the property page when I have
>>> multiple
>>> BC> versions of .net framework on this computer, but that property
>>> page
>>> BC> is not showing up.
>>> BC> BC> Is there any way to fix this, to set which framework is going
>>> to be
>>> BC> used on which website (there are multiple websites on this
>>> server)?
>>> BC> BC> Server is running Windows Server 2003, with all service packs
>>> &
>>> BC> updates on it.  It is also running sharepoint services (the
>>> small,
>>> BC> condensed version, not the full-blown Sharepoint).  That appears
>>> to
>>> BC> work, too.
>>> BC> BC> The 1.1 framework website works, but not the one that is
>>> using
>>> BC> Framework 2.0.
>>> BC> BC> Any help would be greatly appreciated!!!
>>> BC> BC> BC
>>> BC> ---
>>> WBR,
>>> Michael  Nemtsev :: blog: http://spaces.msn.com/laflour
>>> "At times one remains faithful to a cause only because its opponents
>>> do not cease to be insipid." (c) Friedrich Nietzsche
>>>
> ---
> WBR,
> Michael  Nemtsev :: blog: http://spaces.msn.com/laflour
>
> "At times one remains faithful to a cause only because its opponents do
> not cease to be insipid." (c) Friedrich Nietzsche
>
>