Friends of Client Development N ews lette r – March 2006 Introducing our Team Greetings from the Microsoft product team that brings you WinForms! We’re launching this newsletter as an insider's view of what we’re working on - the first in series of monthly newsletters that gives you the latest on our progress in developing new products, our vision for the future, and anything we think you'll find interesting and exciting. We would love to hear from you - send your feedback and suggestions to Rich Ersek ( richarde@microsoft.com ). Current Projects So what have we been up to in the past several months? We’ve just finished up a quality-focused milestone which gave us an opportunity to further improve on our engineering practices. For example, one...

A brief writeup on one of the driving forces behind the Atlas UI framework: enabling structural markup and design... now illustrated via an example. Read More...

Friends of Web Development N ews lette r – March 2006 Introducing our Team Hello developers! We’re the product team that creates ASP.NET, Visual Web Developer (the web project designer in Visual Studio) and most recently, “Atlas”. We’re launching this newsletter as an insider's view of what we’re working on - the first in a series of monthly newsletters that gives you the latest on our progress in developing new products, our vision for the future, and anything we think you'll find interesting and exciting. We would love to hear from you - send your feedback and suggestions to Rich Ersek ( richarde@microsoft.com ). Current Projects So what have we been up to in the past several months? We’ve just finished up a quality-focused milestone which...

I think that the #1 most confusing or misunderstood portion of Site Navigation is the securityTrimmingEnabled flag and the roles attribute on siteMapNodes. This post wil hopefuly clear up some of the confusion. SecurityTrimmingEnabled Firstly, let me be explicit about this: out of the box, securityTrimmingEnabled is meant to be a security feature. By secure, let me use the following definitions (hopefully we agree on them): 1) A page that should not be accessed by a user, but can actually be accessed is not secure. Even if the page is not linked to from any other page. 2) A page that should not be accessed and cannot be accessed is secure. Now, consider this in the context of a web.sitemap file. Perhaps you have a rather simple file like this...

I think that the #1 most confusing or misunderstood portion of Site Navigation is the securityTrimmingEnabled flag and the roles attribute on siteMapNodes. This post wil hopefuly clear up some of the confusion. SecurityTrimmingEnabled Firstly, let me be explicit about this: out of the box, securityTrimmingEnabled is meant to be a security feature. By secure, let me use the following definitions (hopefully we agree on them): 1) A page that should not be accessed by a user, but can actually be accessed is not secure. Even if the page is not linked to from any other page. 2) A page that should not be accessed and cannot be accessed is secure. Now, consider this in the context of a web.sitemap file. Perhaps you have a rather simple file like this...

A user found an interesting issue in the SiteMapProvider code. It seems that if you have a node that has a url such as: "~/home.aspx?p=some text" (notice the space in the query string) and you are actually navigated to that url, SiteMap.CurrentNode doesn't actually return the correct node. The reason for this is that the url actually comes in as: "/home.aspx?p=some%20text". Now, firstly, this is a bug, and it's been filed to be addressed in the future but what (if any) is the workaround? This one is tricky because the issue is pretty deep. You need a custom provider and the appropriate method overridden. When the user raised the issue, I thought about it and decided I could come up with the solution in 5 minutes or let him struggle with it for...