Sometimes, ya just gotta write out the ideas.  Even when they're bad.  VB & XML might be a great idea...

or not.

xml is not a bad solution given some of the nice things that you can do with linq, xml and objects. if you are looking for storage alternative you could also look at www.db4o.com. I am sure that you are familiar with them. easy object storage and retrieval

DTSTTCPW. Then Refactor. So what if it is XML? Once that works, then you can write a wrapper.

XML itself is not uncool. The misplaced use of it is.

So I'm a little confused, are you using XML to simply store some structured data? Or are you using XML to represent the stories?

This is the problem I have with trends, people ignore good solution ideas because it's a technology that is not "trendy" and that can cause all kinds of issues.

XML is not a horrendous technology.  It serves a purpose.  So to completely throw it out because it's not "Alt.NET" is just ridiculous.  Isn't Alt.NET about find the best solution and practice for the job at hand?  Who's to say that it couldn't be XML?

Does this mean the "all clear" has been issued for the Session object in web apps?

;-)

As an admitted DDD slacker I support your choice in the spirit of the same notion of pragmatism that I took away from the Austin Alt.net AHA gathering a little over a year ago.

Rock on.

Despite what many in ALT.NET think - they don't know everything, they aren't always right, and just because they think it's a good idea doesn't make it so and vice versa.

The XML story really only falls apart when people start using it as a programming language, such as NHibernate mappings or StructureMap's old .config stuff.  This same problem would occur if you used JSON, etc.  Data formats do not a language make.

The scenario you're describing sounds like an example of programming in XML, but not knowing your intended usage of these XML files I can't make a judgement call.  A DSL may be a better solution in terms of representing your tests and the steps that need to occur, but you do give up good tooling too...  Not a simple choice was it.

If it makes sense to do it in Xml then do it. If anyone complains, tell them to send you a patch, isn't that how it works? =)

Good point. Every tool has it's merit and can be abused - even the 'cool' ones.

xml might be overused, but the xml hate is even worse.. xml is overused.. that doesn't mean never use xml, and especially doesn't mean you should be desperately trying to find a alterate solution for something xml can do just fine..