Re: Latest patch parses 1.1 pages with 2.0

re:
!> This is calling aspnet-regiis -lk for 2.0.

Actually, that's calling aspnet_regiis -lk

re:
!> There is no default site and you can see that the root site is registered for 1.1.

Yes but, in spite of that, the "Default Web Site" might be registered to 2.0,
and/or the "Web Sites" might be registered to 2.0.

re:
!> Are you telling me that I would get different results if I had checked this
!> from the MMC plugin? I'd be very surprised if that were the case.

What stops you from opening the IIS Manager and seeing for yourself ?




Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
======================================
"David Cameron" <DavidCameron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BCECB068-FD4A-49A1-8831-8B564CABC546@xxxxxxxxxxxxxxxx
I can't confirm that, as I have re-registered all sites with 1.1.

However I do have a command prompt open from before I registered all as 1.1,
but was recieving the error. It includes the results from a call to
aspnet-regiis -lk. It reads:

W3SVC/ 1.1.4322.2407
W3SVC/1370742412/root/ 1.1.4322.2407
W3SVC/1453161142/root/ 1.1.4322.2407
W3SVC/2034039847/root/ 1.1.4322.2407
W3SVC/2080259255/root/ 1.1.4322.2407
W3SVC/2116458577/root/ 1.1.4322.2407
W3SVC/370149253/root/ 1.1.4322.2407
W3SVC/384844167/root/ 1.1.4322.2407
W3SVC/891393290/root/ 1.1.4322.2407

This is calling aspnet-regiis -lk for 2.0. There is no default site and you
can see that the root site is registered for 1.1.

Are you telling me that I would get different results if I had checked this
from the MMC plugin? I'd be very surprised if that were the case.


.

Loading