Not only has SilverLight been official relased (and rebranded from WPF/e) but a nice little paint app to override/replace your basic (oh so basic) windows paint app has been released. Its pretty handy and does most of the stuff I would want out of a paint app and its free and open source so we can pull it apart and look at its guts!
if this article does what i want it to do i will hail Danny Chen, well at least pay more attention to his blogs 😉
Long and short of it, xml site maps have never really sat well with me, i know Gumble has rewritten sitemap stuff before, however the project we are working on is using the xml source (not DB) so i’ll stick to it.
Cheers to SteveE for the help on this too.
Scotts Gu’s reply to AJAX secuity breaches can be seen here
Interesting article on AJAX Security flaws, sighted by Joe On .NET, but some reason its no longer showing on his site(?)
http://www.eweek.com/article2/0,1895,2110554,00.asp
“…. called JavaScript Hijacking—can be found in the biggest AJAX frameworks out there, including three server-integrated toolkits: Microsoft ASP.Net AJAX (aka Atlas), Google Web Toolkit and xajax—the last of which is an open-source PHP-class library implementation of AJAX….”
One line synopsis:
Basically don’t use in built AJAX when sensitive data is being passed, but it is fine on public sites.
Asp.net DropDownList does not work
The two events OnSelectedIndexChanged and OnTextChanged seem to actually check if the value of the dropdown list has changed. When queried what the selected index is it will give you the first value that has the selected value. Basically the OnSelectedIndexChanged is incorrectly named, it should be OnSelectedValueChanged.
Other bugs in this control are .SelectedValue actually returns the lowest indexed listitem with the selected value, and when you would expect .Text to map to the visible text it actually is the corresponding value (so both of these are incorrect in kinda the same way).
Because of this, the OnTextChanged event does actually work “correctly” just not at all intuitively and it appears that it too comes under the nonexistent OnSelectedValueChanged event.
To be honest im a little disappointed that this has persisted through to .Net 3.0, I would love to hear a why this is still the case.
How I have found this (yes i’m sure millions of other have), is a client wants duplicate values with diffent text in a drop down… not sure if there is a real business reason, bu theres the background anyway.
End rant, sorry my firstone was negative… oh well
See you soon 🙂
Rhys
Rhys Campbell 