This article does a great job at showing you a simple example of how to use local browser web storage in conjunction with ASP.NET web methods to save and retrieve the data from a server side database. Even if you aren’t interested in using this functionality in an application you have now, it’s worth reading to know what HTML5 brings to the table as far as storing your data down at the client.
Yay!! Microsoft has released a Web Standards Update for Visual Studio 2010 that adds full support for HTML5, CSS3 and new Javascript features like Geolocation and local storage. Scott Hanselman has a good write-up on this update in this blog post. There you can see some more detail about what exactly it brings to the VS.NET IDE, etc. Or, if you want to skip all that and go right to the download, you can get it here. At this point in time the HTML5 standard is still evolving. Taking that into consideration, Microsoft plans to provide additional updates every quarter or so to keep up with new features, changes to the draft, etc.
By the way, if you still aren’t familiar with all of the cool things that HTML5 brings to the table you should definitely check out this free online book, Dive Into HTML5, by Mark Pilgrim.
Visual Studio 2008 is not without its faults. They did however add some nice features in the 2008 release such as JavaScript debugging. This feature is great when you need it, but can drastically slow down your debugging experience if you don’t need it or use quite a few “script heavy” controls like Telerik Radcontrols.
So after dealing with this for a while and taking enough productivity hits I decided to find a way to disable the Script Documents folder that shows up when running in debug mode.
It didn’t take long to stumble across this blog post where the blogger made a VisualStudio add-in to make turning this on and off as needed easy via a toolbar button. After reading the post and downloading the utility I was debugging without the old lag that I had before caused by all of the JavaScript documents that were loaded.
If you’ve run into this and feel this would be helpful, I can say that it seems to be working fine for me. I was a little worried too considering I run Windows 7 but it seems to still work well without any permissions issues.
A while back I had a need to dynamically re-size an iFrame’s height and found a solution using a jQuery plug-in called autoHeight. What I later found was that this solution provided poor results with Internet explorer when my iFrame’s contents were fairly large and frequently changing (i.e. via navigation inside the iFrame).
It took quite a bit of tinkering but I was able to come up with a solution that works (and works well) in IE, Firefox, Safari and Chrome. It still uses jQuery but doesn’t depend on a plug-in. Here’s the code in case you’re looking for the same thing:
First, the iFrame…
<iframe src="Page1.htm" id="MyFrame" frameborder="0" marginheight="0" marginwidth="0" width="800px" height="100px" scrolling="no"></iframe>
Next, the JavaScript to resize it…
<script type="text/javascript"> function sizeFrame() { jQuery("#MyFrame", top.document).css({ height: 0 }); var heightDiv = jQuery("#MyFrame", top.document).contents().find('body').attr('scrollHeight'); jQuery("#MyFrame", top.document).css({ height: heightDiv }); } jQuery(function() { sizeFrame(); jQuery("#MyFrame").load(sizeFrame); }); </script>
This line is needed to initially initialize the height so that it works in Safari and Chrome. Without this line the window will never shrink to fit smaller content, it will just retain the last biggest height.
jQuery("#MyFrame", top.document).css({ height: 0 });
I have been going back and forth banging my head against a wall trying to fix a JavaScript error that was happening on my Reporting Services ReportViewer control when the View Report button is clicked. The error was a JavaScript error and seemed to be related to using something AJAX related on the same page as the ReportViewer control, but it took me a while to figure out what it was and fix it. All of the problems I saw on the web related to using either an AJAX update panel or one of the extenders in the AJAX Control Toolkit. Unfortunately for me I wasn’t using either one of them so trying to figure this one out was tricky.
The specific JavaScript error was:
Microsoft JScript runtime error: ‘this._postBackSettings.async’ is null or not an object
My page was setup where I had a master page with an AJAX menu on it (Radmenu to be specific). In order to use the Radmenu you need a ScriptManager object. Other than the menu, I didn’t have any AJAX related controls on either the master page or the content page.
What I eventually figured out was that my report pages (which use a base class) needed to disable partial rendering. To do this, you must do it in your page’s init event. If you do it after the init you’ll get an invalid operation exception. Here’s the code in the base class (you can put this in your code behind if you’re not using a base class):
Private Sub Page_Init1(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Init ' Make sure this page has a master page If Not IsNothing(Me.Master) Then Dim masterScriptManager As ScriptManager masterScriptManager = CType(Master.FindControl("MasterScriptManager"), ScriptManager) ' Make sure our master page has the script manager we're looking for If Not IsNothing(masterScriptManager) Then ' Turn off partial page postbacks for this page masterScriptManager.EnablePartialRendering = False End If End If End Sub
Just in case others stumble across this and are trying to solve their problem, here are some of the links I landed on when trying to solve the problem:
© 2012 Don Kitchen · Proudly powered by WordPress & Green Park 2 by Cordobo.
Valid XHTML 1.0 Transitional | Valid CSS 3
