I can tell you why did this at our company - it allows for a much faster
development process. Since we have a framework that has been tested already,
usually the only thing we have to build are the UI pieces, and put in any
custom business logic for that project.
We actually have 2 frameworks - one for internet applications and one for
windows/desktop applications. The frameworks have all the security and data
access stuff built in, so it makes the development a lot faster and easier
to test. Plus, it's something we can easily get new hires to work in, so all
our code is fairly consistent.
I know that with our internet framework, (which we also have a site
"template" created to speed things along, as well), we can knock out a very
robust, feature-rich application (application-level security, dynamic,
role-based content and menus, and a site for administration of the data) in
a couple of days.
Theresa
"DraguVaso" <pi**********@hotmail.com> wrote in message
news:uL**************@TK2MSFTNGP09.phx.gbl...
Hi,
Some time ago I spoek to a guy who proudly announced that his company
build
their own Framework tu be used as a base for their .NET-applications for
their customers. In my new job somebody suggested me to do the same.
But what the heck do they want to do with that? They both did it/wanted it
for the DataLayer and stuff, but I don't see really a big advantage in
doing
these things. So I have this questions:
- What should such a Framework include?
- What benefits does it have?
- How do you write it?
- Anybody has a sample of such a thing?
Any answers, discussions, etc would de nice regarding this subject.
Pieter