Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

In a VB to .NET conversion, what techniques can be used if I have decided to keep the information on the client?

0
Posted

In a VB to .NET conversion, what techniques can be used if I have decided to keep the information on the client?

0

If you decide to store your instance on the client, you can use some of the following techniques: • View state. The control.ViewState property provides a dictionary for retaining values between multiple requests for the same page. This information is automatically stored. When the page is processed, the current state of the page and controls is hashed into a string and saved in the page as a hidden field. When the page is posted back to the server, the page parses the view state string at page initialization and restores property information on the page. • Hidden form fields. You can create hidden fields on a form that are not visibly rendered by the browser. With this technique, you can set properties just as you can with a standard control. When the page is submitted to the server, the content of the hidden field is sent in the HTTP Form collection along with the values of the other controls, which allows you to store information directly in the page by way of the hidden fields. • Co

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123