Wow. Where this stuff is a struggle with snippet compiler, LinqPad has great visualizers that shows you the state of any object without work (foreach object in collection writeline yadda yadda) on your part.

PostPHONE?

And this is a slightly disorganized and unclear rant about XML in source control. Tools aren't serializing things in a predictable order; XML becomes impossible to merge automatically, guy goes nuts when no acceptable solution is proposed.

Three down and at least two more to go.

Nice observation. Another example where not being explicit in your code can end up kicking you in the ass.

Dunno.

"Does storing your password in the users.xml file without encryption bother you? It definitely bothers me so I sent an email to Mads asking him about this topic. He mentioned to me that some people didn't like storing the password in an encrypted format. Seems strange to me but okay. "

Seems strange to me by NOKAY. I'm going to take a peek at the code and see how hard it is to hash the passwords this weekend (if I can get time aside from retiling my bathroom, working on my split-file join app, and working on my GF's survey website).

http://www.codeplex.com/blogengine/Thread/View.aspx?ThreadId=19293

Supposedly there is resistance to hashing passwords in the BlogEngine.NET team.

Wat?

Mads needs to read this article: http://statestreetgang.net/post/2008/04/A-NET-Cryptography-Primer2c-Part-Two.aspx

Pavatar is nice, but appears to require you host your own website (or at least have a page somewhere on the internets). Most numbnuts don't have this.

What we need is an avatar service that tricks Google images to host your avatar for you.

That website design makes the baby Jesus cry.

Dumbasses.

Thanks for the vote of confidence. The whole deal with key containers is that its not documented very well and I haven't been successful in storing key pairs reliably in anything other than the machine store. Storing it per user is more secure, but I'm still working on getting it right.

Next one is symmetric algorithms and the last one will be probably a two-parter on public/private key encryption. Or it will be overly simplified. I'm still lacking some info about asymmetric key storage.

Never paid much attention to HAVING. It was wrong to do so, and I apologize.

Very nice. Thanks!

I'm the anti-drama, so I'll stay away from this. You won't find me on MySpace, either.