+972 52-548-6969
Quotes of the weeks
Those are courtesy of Jdn's post.
If you don't, you are stupid, a Mort, or, god forbid, an architect.
Oh my, I am not sure if this was intended to be amusing, but I certainly find it so.
Similarly, it is okay to use a Visual Studio designer. It is even okay to use drag and drop. There, I said it. Let me say it again, with feeling: IT IS OKAY TO USE DRAG AND DROP.
This comes at a very appropriate time, since I just spent a few hours wresting with a drag & drop code-gen solution. I got it to work, even. But the end result is not what I want or need, so I am going to rewrite it by hand tomorrow. So there, it is perfectly OK to use Drag & Drop, and I would probably never do anything in WinForms without the designer.
And just a note about the Alt.NET Agilistas, I am afraid that this term is reserved for Wendy and Oxana.
Comments
Yes, it was supposed to be amusing, glad you liked it.
Didn't know the term was taken, so changed the title. Thanks.
Is it AW*? If so, I'd love to hear about problems and suggestions.
Yes, it is.
And the main issue wasn't AW, it is that I am trying to get it to work against a DB schema from hell, the MS CRM one.
At that point, it is simply not worth it.
To give you a clue, ~80 properties per class, no FK, hell & bedamned forced naming convention.
I don't blame AW for this, in fact, I am applauding it for taking me that far. But when a source file is over 1500 LOC, that is a problem, especially when I need 7 properties or so, no more.
Comment preview