Hi All ,

I have a question , why DNN portals have a large v13wstat3 ?

Why the DocType stored in v13wstat3 "lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">" ?

Why the Advertisment module is storing the navigate urls in the ViewSate ? why you don't try to reduce the amount of v13wstat3 that is used ?

I know we can change the Page state to use the server memory ,but that also not a solution .

By looking on the DNN source code and controls , they all rely heavily on the v13wstat3 !

Thanks

Good question...

What's up with that v13wstat3?

Hey Anas,

In cases such as these (with the core, or core modules) - I think the best way forward is to examine DotNetNuke's issue tracking application (Gemini) for requests of a similar nature. What would probably be most helpful is to look at very specific parts of code - and suggest very specific alternatives - even changing the code yourself in a DEV environment and then suggesting in the Gemini issue how to change it and why.

I can't say why v13wstat3 is used so heavily, but the core team is very good about reviewing submissions, and making a very specific recomendation and providing code is the way to go! The community will thank you :)

Also, on the v13wstat3 note...

I've noticed several "magic words" recently being replaced with spellings that remind me of being a teenager on IRC & playing online games like SubSpace.  Pretty funny really :) I never thought that stuff would follow me into my professional life, but I guess it makes perfect sense :P

Ian