viewstate .net 1.1 vs 2.0

  • Thread starter Thread starter Simon Gorski
  • Start date Start date
S

Simon Gorski

Hi,
I have a webfarm - every server has the same machinekey. - Everything works
fine with the asp.net viewstate (every server run with .net 1.1)
Now I want one server upgrade to .net 2.0 - so I set the machinekey as the
same with 1.1.

But it looks like that .net 1.1 produces other viewstate as .net 2.0?

thanxs!

Simon
 
Simon,
It is highly likely that 1.1 and 2.0 generate Base64 Encoded viewstate
hidden fields that are different, even if the machine key is the same across
machines. I think you want to be sure that all the cows on the farm are the
same model.
Peter
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

SQL setup for Session 1
1.1 and 2.0 of same application on load balancer 1
Validation of viewstate MAC failed 3
.NET version question 2
Problem in Sharing Session between ASP.NET 1.1 & ASP.NET 2.0 1
asp.net 2.0 app using .net 1.1 library 2
Validation of viewstate MAC failed 1
Viewstate Encryption 4

Back
Top