end and are now getting call after call on our techsupport line. It appears that 2.0 handles the cookieless sessionID
differently than 1.X. Now every one of our customers that had our site
bookmarked with their sessionID in the URL is getting a server error (404)
when they try to open it. And I can't even trap the error and give them a
nice explanation since they aren't even getting into the app.
Good job Microsoft! Very smooth upgrade path.Hello,
you really should present this feedback on ASP.NET Forums's as that's where
MS's Web Platform & Tools team listens
Migrating from ASP.NET 1.x to ASP.NET 2.0
Discuss issues about compatibility with and migration from previous versions
of ASP.NET.
http://forums.asp.net/180/ShowForum.aspx
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke
"Chip" <chip@.intradata.com> wrote in message
news:%23Y3Szz7OGHA.1180@.TK2MSFTNGP09.phx.gbl...
> We upgraded this w
end and are now getting call after call on our tech> support line. It appears that 2.0 handles the cookieless sessionID
> differently than 1.X. Now every one of our customers that had our site
> bookmarked with their sessionID in the URL is getting a server error (404)
> when they try to open it. And I can't even trap the error and give them a
> nice explanation since they aren't even getting into the app.
> Good job Microsoft! Very smooth upgrade path.
>
0 comments:
Post a Comment