asp.net 1.1 X 2.0 compatibility issue

23 Jun 2006 1:59 PM

VR

Hi, I developed a web app a few months ago using asp.net 1.1. Last week,
the server hosting this app was upgraded to asp.net 2.0 (that is said to be
100% compatible).

Well, since the upgrade the calendar control behaves in such a crazy way, I
mean:

1. in the page_load event I set calendar.SelectedDate = Now

2. the date in the calendar shown in the browser is not selected

3. using the debugger I found that the date exists in memory in the right
way (calendar.SelectedDate equals Now)

4. trying to insert a record in a access database I got an error saying the
parameter is missing

5. if you click on a date in the browser's calendar, the date is correctly
selected and the record is inserted without a problem

PS: it's an asp.net 1.1 app running on an asp.net 2.0 environment

PS2: if I move this app to an asp.net 1.1 environment, everything works fine

thanks for any clue,
regards,
Victor

27 Jun 2006 2:29 PM

Washington Moreira

100% Compatible???

I think that you should implement a side-by-side environment, until your
code have been ported to 2.0 Version.

http://msdn.microsoft.com/netframework/programming/breakingchanges/runtime/default.aspx

tks

Washington Moreira

Show quoteHide quote

"VR" <vc***@hotmail.com> wrote in message
news:Ou1sN5slGHA.2204@TK2MSFTNGP03.phx.gbl...
> Hi, I developed a web app a few months ago using asp.net 1.1. Last week,
> the server hosting this app was upgraded to asp.net 2.0 (that is said to
> be 100% compatible).
>
> Well, since the upgrade the calendar control behaves in such a crazy way,
> I mean:
>
> 1. in the page_load event I set calendar.SelectedDate = Now
>
> 2. the date in the calendar shown in the browser is not selected
>
> 3. using the debugger I found that the date exists in memory in the right
> way (calendar.SelectedDate equals Now)
>
> 4. trying to insert a record in a access database I got an error saying
> the parameter is missing
>
> 5. if you click on a date in the browser's calendar, the date is correctly
> selected and the record is inserted without a problem
>
> PS: it's an asp.net 1.1 app running on an asp.net 2.0 environment
>
> PS2: if I move this app to an asp.net 1.1 environment, everything works
> fine
>
>
> thanks for any clue,
> regards,
> Victor
>
>
>
>
>