On Tue, Aug 17, 2010 at 10:46, Frans Bouma <[email protected]> wrote: > > > 2) it's doing work that's unnecessary, as you're > > testing work > > > which > > > can be done by a machine which doesn't make mistakes. > > > > > > Did you read the part where I say this is autogenerated? > > Generated by what exactly? > > > > A script. > > which grew on the ScriptTree? Or did you write it yourself? Another > part of a chain, which can fail or contain bugs. >
It grew on the ScriptTree. You have no idea how much time I saved by buying one of those :-D Also, did you know that script run logs are edible? They taste delicious with BBQ sauce. > > Test is not runtime. We seem to have a fundamentally different > undestanding > > of what the build process is. > Apparently. > Luckily I'm just a salesman writing micky mouse apps, eh? ;) > LOL... I never said that :-) ...not that there's anything wrong with those apps....... > > XML is neither less nor more human readable/writable than C#. > right. Because it comes with a proper compiler, as C# does? > Exactly. In fact, I have three compilers: - XML well-formedness compiler - XML Schema validator - BuildSessionFactory The first two even run in the background, in addition to being called by the third. And that one is a mouseclick/keystroke away. > > Forgive me if I prefer IDEs that assist me with writing text to visual > tools > > like the one you sell. I am more productive with the former. > > 'you sell' ? Like the one you 'wrote' would have been more > appropriate. I'm not selling anything, I only designed and wrote it from > scratch. Like you did too. Oh wait... > Point taken, wrote AND sell. Don't read too much into that. I'll go one step further and say that your product is probably better than 90% of the code generators. I'm only saying *I* don't use them. > > > WHAT? 8-O > > > Automapping is model-first runtime code generation. > > > > oh? so, when you change some classes, it will... work on > your > > DB? > > Oh, you have to trash the db, so how are you going to 'maintain' > > things in > > production then? > > > > Change scripts. > > yeah, those written by hand after carefully examining by hand what > changes you made? Or by relying on diff tools which compare DDL SQL scripts > however they always fall flat on their face when they have to deal with > renames, type + renames, field moves, multiple fk + field changes, those? > OK, how do you do it? Diego -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
