12 Sep 2006
As I mentioned in my CSS Adapters Beta 2 entry, the asp:Menu control does not work well with Safari. As I was trying to research how to make the control compatible ( before I knew about the CSS Adapaters ), I searched Google for workarounds and found the article Using Device Filters ( and making Menu work with Safari ). This was a new feature in ASP.NET 2.0 that I had never heard before. Using device filters you can prepend a browser type to your aspx tag attributes to change the behavior of the tag.
For example you can do the following:
<pre>ÂŤ/span>asp:Label
id=âlblBrowserTypeâ
runat=âserverâ
IE:Text=âHello Internet Explorerâ
Mozilla:Text=âHello Mozillaâ
Safari:Text=âHello Safariâ /></pre>Althought probably not useful, when viewed the above code will display âHello Internet Explorerâ if you viewed the page with IE, âHello Mozillaâ if you viewed the page with Firefox, and etcâŚ
The device filters use the same Browser Definition File Schema information that I shared in my HttpBrowserCapabilities entry.
Unfortuantely, I wasnât able to get the menu to look like I wanted in Safari using device filters, but it did enlighten me to the new feature.
Read More »
09 Sep 2006
For those of you who would like more control of your HTML output from ASP.NET 2.0, then check out the newly updated CSS Adapters Beta 2.
At one point I looked into using âCSS Adapters Beta 1â because the native asp:Menu HTML output does not work well with all browsers ( mainly Safari ). However, my direction was altered in another direction that didnât need the asp:Menu control, so Safari compatibility with the menu was no longer an issue.
Anyway, I know there are some hardcore CSS gurus who will do anything they can to not use tables for non-tabular data. If that describes you, or if youâd just like a little more control of your HTML output, then check out the CSS Adapters Beta 2.
Read More »
08 Sep 2006
The current project I am working on involves a website that is external facing. Since I am using CSS and JavaScript in ASP.NET 2.0 older browsers may not behave as expected. Therefore, I implemented White, Black, and Gray browser lists.
Initially, I used a JavaScript Browser Sniffer Library written by Pau Garcia i Quiles, but then I became aware of the HttpBrowserCompatibilites class in .NET!
I just finished rewritting the lists using .NETâs Browser object ( located off the Request object ). If you are interested in knowing how .NET figures out all this information check out the Browser Definition File Schema. You can find all of the browser definitions on your machine at â%SystemRoot%\Microsoft.NET\Framework\version\CONFIG\Browsersâ. Its very interesting to look through the files and see what information .NET uses to determine your browser information.
Read More »
23 Aug 2006
A new feature of Visual Studio 2005 is the introduction of Debugger Visualizers. They offer an advanced, customized data display while you are running your application under the Visual Studio Debugger.
Here is a list of Debugger Visualizers that I have foundâŚ
<ul>
<li>GUID Debugger Visualizer for Visual Studio 2005 by Jeff Bramwell</li>
<li>WindowsIdentity Debugger Visualizer for Visual Studio 2005</li>
<li>Conchango Xml Visualizer for Visual Studio 2005 (RTM) by Howard van Rooijen</li><li>ControlTree visualizer by K. Scott Allen</li>
<li>Visual Studio 2005 Cache Visualizer by Brett Johnson</li>
<li>Visual Studio 2005 Control Visualizer by Brett Johnson</li>
<li>Regex Visualizer Kit by Roy Osherove</li>
</ul>If you are interested in developing your own Debugger Visualizer, then here are some tips.
Read More »
22 Aug 2006
A college of mine asked me if I knew the shortcut for getting the matching brace/bracket/parethesis in Visual Studio 2005. I didnât know, so in my search for the answer I ran across a useful page with lots of useful Shortcuts for Visual Studio 2005.
By the way, the shortcut for matching a brace/bracket/parethesis is âCtrl-]â.
Read More »
