My feelings also, you get that "Thats a bit dirty, but I'll tidy it up
later" feeling and six months later the dirty code turns up in production.
I wasn't actually thinking about UI design more so the data tier, this is
the area I spend most of my time developing and yet it seems to be mostly
repetative.
I have the basics already developed using reflection and custom attributes
but I'm undecided as to whether or not to develop it any further, I know
I'll benefit from it in it's present state but I'm interested in other
people views. Some kind of automatic generation of the tables,
relationships, fields and attributes would be a bonus, but may take some
time to develop.
Chris.
"Kirk Graves" <kr***********@yahoo.com> wrote in message
news:OC****************@TK2MSFTNGP10.phx.gbl...
I for one do all my prototyping in VS.net. Very easy to put together a
good looking UI. The secret to prototyping though is to Never use the
prototyped code in the production project. Always start over with a clean project
once the user accepts the prototype. This avoids having all the garbage code
we use in a prototype carrying forward to production.
Kirk Graves
KRGIT Software
"Tilted" <pu***@gvygrq.pb.hx (ROT13)> wrote in message
news:OD****************@TK2MSFTNGP10.phx.gbl... Does anyone here use prototyping tools? I'm building one myself as I
feel like I'm doing the same thing over and over again with the majority of
my projects, how do people generally feel about them? Do people ever use
the generated code in production?
Thoughts appreciated.
Chris.
