Last post Sep 16, 2009 03:32 AM by DaveRuss
Sep 15, 2009 10:17 AM|beaucroco|LINK
I made a Dynamic Data application with a custom HideColumnFieldsManager. (By following Steve tutorial :
In addition, I added a table named 'scope' which contains names of all my tables and boolean to display or not:
SCOPE table :
table_name | displayable
"table 1" | "yes"
"table2" | "no"
"table3" | "no"
I made necessary changes in code source, to make it work. It's work, but I need to recompile the application sothat it's work. It's a problem for me: if an administrator set a table_display_attributes to false, he will still see
the table availaible...
Steve answered this problem by :
the issue is Metadata is not loaded after application start so to programmatically do this you will need to recycle the application using:
This should get the latest metadata updated.
It works ! But it clears all my Session variables !! So I have to find a trick to solve that.
Please help. Thx.
Sep 15, 2009 11:03 AM|DaveRuss|LINK
Move your session out-of-process. Either store it on a Session Server or in a SQL Server Database.
Useful article comparing the options here
Sep 15, 2009 12:02 PM|beaucroco|LINK
Thx a lot DaveRuss, this is a solution.
But I would like to avoid things like :
"an administrator would also need to create the ASPState database by running the
InstallState.sql script found in the WinDir\Microsoft.Net\Framework\Version folder"
I'm not sure it's possible for me. I would like to make easy the release of my WebApplication.
More over, my session variables are used in all my pages, that's why this kind of solution will decrease significatively performance of my WebApplication :(
Do you think there is another solution ?
Sep 16, 2009 03:32 AM|DaveRuss|LINK
To be honest, I think forcing your appdomain to unload is going to hurt your performance much more than storing session in an external process or a database.
Another option would be that everything you have stored in session could be stored in ViewState instead, but you would have to make sure it was in ViewState in every page, whereas the same session is available to every page.
If you have session inProc you will always lose it if you do an AppDomain unload - there is no way around that.