Many developers persist DataSets between postbacks by doing something like this:

Session["dsPatient"] = (DataSet)this.oPatient.GetPatientByID("123456")

I persist the patient's data between postbacks in this way. These are small one record datasets so I don’t take a big resource hit. – This worked fine in asp.net 1.0 and 1.1

But in asp.net 2.0…
Any page that has data persisted in this manner *cannot* redirect to a page that has aspcompat=true in the page directive without throwing asp compat errors. Remember that ASPCOMPAT should be set to true when your pages incorporate Visual Foxpro COM interop.

OK... What is going here? Is this a security issue that is now present in asp.net 2.0 or is it a flaw? This is reproducible on all of my pages that I persist data in this way in asp.net 2.0

Any thoughts?

Neil Gorin