#left { float: left; } #main { float: left; } #right { float:right; } <div id="left"> </div> <div id="main"> <div id="right"> </div> </div> Try that. I think it will do what you described.

This error usually happens when your web app runs on a web farm but the machineKey isn't the same across all servers. Is this an issue in production? Check out this article on MSDN for more info. http://msdn.microsoft.com/en-us/library/ms998288.aspx[^]

If you aren't decided yet on the charting library, check out the Microsoft .Net charting controls. It includes features like clickable areas. http://msdn.microsoft.com/en-us/library/dd456632.aspx[^]

Without streaming, the entire video will need to download before it starts to play. I don't understand why streaming is not an option here. It is generally built into the web server. You might not want to host a separate server just to host media content, but streaming should be possible. What type of server is the site hosted on?

'login' to what? The web application? sql server?

Nope. Excel can open a CSV file directly. :-D

What browser are you using? If it's IE, try adding the url to the list of trusted sites.

True, cookies will not work if the user has them turned off. I think you might need to just come up with a custom solution for this.

Take a look at Export DataTable to Excel with Formatting in C#. It should be a good starting point.

Have you looked at this article? Version Tolerant Serialization The callbacks should be able to do what you need.

It sounds like your looking for something like 'Server.Transfer()'. The page executing the incoming request will stop processing and pass control to a new page you specify like a method call.

Have you checked MSDN? They have sample code to look through. http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.treeview.aspx[^]

Have you tried using a temporary cookies to store each search term submitted to page2? The methods Asp.net uses to store state (viewstate, hidden fields, etc) are generally designed to work with POST requests so I don't think there is any client-side feature that will work. You could also manage a string of submitted requests in javascript but the advantage of the cookie is that all the processing can be done on page2.aspx and return the cookie to the user after each request.