Well, my two-year stint for the real estate company I was working for is over, and I'm back to consulting again. It is a welcome change for me, because educating my business partners on technology was a daily exercise in futility.
I'm available for on- or off-site consulting work, and my rates are flexible. Just use the contact form to drop me a line, and we'll see how I can lend a hand!
I have a scenario where I think I've found a bug in the SiteMap API in ASP.NET 2.0. The scenario is this:
- Create two separate .sitemap files in your application.
- Create two SiteMapProvider references in the web.config file. Give them unique names and make one the default.
- Create a new webpage. Drag a SiteMapDataSource control onto the page, and specify the name of the non-default SiteMapProvider in the "SiteMapProvider" property.
- Drag a Menu control onto the page, and configure it to use the SiteMapDataSource control on the page.
There are two things that I see happening, and I'm wondering ig anyone else sees this:
- At Design-time, the Menu will bring up data from the default provider, regardless of the provider you specify.
- At runtime, the Menu will not populate with any data.
Is this an issue just with my setup, or are other people seeing this? I dug through the code in Reflector, and I think I found a bug, but I want to make sure I'm not the only one experienceing this first.