Sample Sql SiteMapProvider with SecurityTrimmingEnabled
Creating large flat classes for data binding is one way of doing things. But you should check out this article before anyone decides to tightly couple your object model with your data representation. Mike has put this down beatifully.
http://blogs.msdn.com/mikechr/archive/2006/05/17/600697.aspx
This was a very simple requirement to hide the currently updating controls. I first ran to the the forums and came across this. The trick was quite simple. When we depend control inside the updatePanel this technique fails. The idea is to wrap the update panel inside say another container like a div and set the control ID to that. The below script triggers the hiding of the control and kicks off the UpdateProgress.
<script type="text/xml-script">
<page xmlns:script="http://schemas.microsoft.com/xml-script/2005">
<components>
<control id="GridContent" visibilityMode="Collapse">
<bindings>
<binding dataContext="_PageRequestManager" dataPath="inPostBack" property="visible" transform="Invert" />
</bindings>
</control>
</components>
</page>
</script>
[Atlas] rules :)
For those of you guys who arent convinced yet, I have attached a hello world version to this.
Here's a great article you might be interested in:
ASP.NET Home: ASP.NET 2.0 (codenamed ASP.NET Whidbey) is the next version ofI was new to the showModalDialog Script on IE. Then I came across a problem with new browser windows being brought up with server content in the dialog This is the solution i came across
I noticed that the following is an issue thru which people often run: when you show an aspx page (or any server content in general) in a dialog by mean of the JavaScript ShowModalDialog method, at the first postback you usually witness the instance of a second window, his time a full blown browser, holding in your output.
There is an easy workaround to the situation, but surprisingly it seems that few people knows it: so I'm posting it.
The trick is showing a static page , a simple .HTML, in the ShowModalDialog call; such page should hold the active content (your .aspx) in an IFRAME. Subsequent posts will be confined inside the iframe, hence restoring the intended user experience.
UPDATE
J proposes a more efficient system: <base target="_self"> in the header of the aspx page yields to the same result. Thank you J :-)
protected void Application_BeginRequest(Object sender, EventArgs e)
{
string prefix = Request.Url.Host.ToUpper();
if(prefix.StartsWith("BALTIMORE"))
{
Context.Items["PREFERENCES"] = // Load Baltimore preferences
}
else
{
Context.Items["PREFERENCES"] = // Load default preferences
}
}http://odetocode.com/Articles/111.aspx