I have a ViewState persistence module that works perfectly on my local machine, but when I move it to our Dev environment, it does not. There are no errors, but the ViewState gets rendered in the page output as if the module did not exist at all.
I have checked everything I can think of including the correct code on the server, the SQL connection string where the ViewState is being stored (yes, the code & server has access to the database as we are using the exact same database to store Session state (just different tables) and I can see entries being added for Session state.
As I alluded before, it is almost as if the control adapter in the .browser file is being ignored (or overridden--is that even possible?).
Notable differences: my box is Vista w/IIS 7 (yes, I am testing with IIS 7, NOT the VS2010 mini-server). The server is Server 2003 w/IIS 6. Both my boss and I are sure this was working at one point, but as it is "hidden" from normal view we don't know when it stopped.
I can provide more details if someone needs, but again the code itself works on my local box and is pretty much from the SDK.
View Complete Post