DNK has a spanking new server up and running like clockwork. Stability problems are a thing of the past. Our new monitoring service reports 100% uptime since the move!
14
kicks
published 1 year, 2 months ago, submitted by marshp3 marshp3 1 year, 2 months ago

geekzilla.co.uk — ViewState is a great feature, but it can get really bloated with data, especially if you have loads of controls on a page, repeaters etc. You could think about setting enable viewstate to false, but you'll need it for posting pages back. This tutorial moves the viewstate to a SQL database, by implementing a simple class that all your pages will inherit from.

Add a comment 2 comments | category: | Views: 71 | Get KickIt image code
Move ASP.Net ViewState to SQL Server
tags: | tag it

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:

Comments:
"You could think about setting enable viewstate to false, but you'll need it for posting pages back"

That's not true.

You can kill viewstate for your whole app, and postbacks work fine.

The only time they don't is if you postback and present the user with the same page they just posted, then the controls would not be prepopulated, so it depends on the behavior of your app.
posted by chrcar01 1 year, 2 months ago
In the "Save" method why are they creating the hidden input element with the viewstate? Seems very redundant.
posted by DavidP 1 year, 2 months ago



information Login or create an account to comment on this story

Related Stories:
 

Search: