Modelers / code generators

[Mark]

Are there good modelers / code generators for C#
I looked into Deklarit. The only problem I have with i
Is that it uses dynamic SQL, no stored procs.
Don’t know if that is the best way to architect n-tier application
I am looking for something similar to that program but capable of creating stored procs

Thanks

[Francois Beaussier]

"Mark" wrote :

Are there good modelers / code generators for C#?
I looked into Deklarit. The only problem I have with it
Is that it uses dynamic SQL, no stored procs.
Don't know if that is the best way to architect n-tier application.
I am looking for something similar to that program but capable of creating

stored procs.

Have a look at OlyMars, it is great !

http://www.microsoft.com/france/msdn...rs/default.asp

enjoy :)

--
Francois Beaussier
Fr******@3ie.org.remove

[Frans Bouma [C# MVP]]

Mark wrote:

Are there good modelers / code generators for C#?
I looked into Deklarit. The only problem I have with it
Is that it uses dynamic SQL, no stored procs.
Don’t know if that is the best way to architect n-tier application.
I am looking for something similar to that program but capable of creating
stored procs.

Why are you focussed on Stored procedures? I mean: generating stored
procedures is the same, semantically, as generating Dynamic sql on the fly,
with bigger disadvantages: the maintenance of the procs is killing (replacing
a proc with another one, requires you to remove the old proc, however that
may break an app etc.)

Dynamic SQL is in the long run more efficient, both in
maintenance/development and in processing speed.

FB

--
Get LLBLGen Pro, the new O/R mapper for .NET: http://www.llblgen.com
My .NET Blog: http://weblogs.asp.net/fbouma
Microsoft C# MVP

[Mark Goldin]

Well, I don't think anybody has a definitive answer about
dynamic SQL versus stored procs.
I am personally just not ready to give up on SPs.

"Frans Bouma [C# MVP]" <pe******************@xs4all.nl> wrote in message
news:xn***************@msnews.microsoft.com...

Mark wrote:

Are there good modelers / code generators for C#?
I looked into Deklarit. The only problem I have with it
Is that it uses dynamic SQL, no stored procs.
Don't know if that is the best way to architect n-tier application.
I am looking for something similar to that program but capable of creating stored procs.
Why are you focussed on Stored procedures? I mean: generating stored
procedures is the same, semantically, as generating Dynamic sql on the

fly, with bigger disadvantages: the maintenance of the procs is killing (replacing a proc with another one, requires you to remove the old proc, however that
may break an app etc.)

Dynamic SQL is in the long run more efficient, both in
maintenance/development and in processing speed.

FB

--
Get LLBLGen Pro, the new O/R mapper for .NET: http://www.llblgen.com
My .NET Blog: http://weblogs.asp.net/fbouma
Microsoft C# MVP

[Frans Bouma [C# MVP]]

Mark Goldin wrote:

Well, I don't think anybody has a definitive answer about
dynamic SQL versus stored procs.
I am personally just not ready to give up on SPs.
I'm not saying you should, at least not for specialized programs, like
extensive calculations on a lot of data, often this is done better in the
database to avoid pulling millions of rows into .NET. I'm more referring to
CRUD operations on rows using stored procedures, the vast majority of actions.

What I'm interested in is your reasoning behind holding on to stored
procedures. Could you please elaborate on that decision a bit? thanks :)

Frans.

"Frans Bouma [C# MVP]" <pe******************@xs4all.nl> wrote in message
news:xn***************@msnews.microsoft.com...

Mark wrote:

Are there good modelers / code generators for C#?
I looked into Deklarit. The only problem I have with it
Is that it uses dynamic SQL, no stored procs.
Don't know if that is the best way to architect n-tier application.
I am looking for something similar to that program but capable of creating stored procs.

Why are you focussed on Stored procedures? I mean: generating stored
procedures is the same, semantically, as generating Dynamic sql on the

fly,

with bigger disadvantages: the maintenance of the procs is killing

(replacing

a proc with another one, requires you to remove the old proc, however that
may break an app etc.)

Dynamic SQL is in the long run more efficient, both in
maintenance/development and in processing speed.

--
Get LLBLGen Pro, the new O/R mapper for .NET: http://www.llblgen.com
My .NET Blog: http://weblogs.asp.net/fbouma
Microsoft C# MVP