Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

In-house Frameworks vs New C# Technologies

If we have developed our own ORM framework and the framework is working fine over the years then why should we learn and use brand new .net technologies like LINQ or Entity Framework or NHibernate or CSLA.NET for our upcoming software projects?

Note : New frameworks need new effort to learn and teach.

Note : This is just an analogy.

like image 444
user366312 Avatar asked Sep 03 '09 14:09

user366312


People also ask

What is framework and types of framework?

A framework provides a foundation for developing software applications. Software engineers and developers use a framework as a template in order to create websites and applications. Professionals do this by adding code to a framework, then personalizing it for their specific purpose.

What is the purpose of a framework?

In general, a framework is a real or conceptual structure intended to serve as a support or guide for the building of something that expands the structure into something useful.

What is framework with example?

A software framework is built on top of a programming language. For example, Rails, also known as Ruby on Rails, is a web framework built on top of the Ruby programming language. Django and Flask are two different web frameworks built on top of the Python programming language.

What is a framework and what types of problems does one tend to solve?

What is a framework? A framework provides a high-level, yet a foundational structure for solving a particular type of problem. It can be considered as a model, which visually depicts the key building blocks of the problem being analyzed.


2 Answers

  1. Because new developers will know the newer frameworks, but not yours
  2. So you don't have to waste time maintaining code that Microsoft would maintain for you

BTW, "LINQ", per se, is a technology complementary to your framework

like image 153
John Saunders Avatar answered Nov 02 '22 18:11

John Saunders


Because what you currently have is proprietary and unknown... and you want to still be able to develop your code efficiently if you get new staff.

There's nothing wrong with writing your own ORM, but maybe Entity Framework 2 contains some stuff you didn't think about - and there's a whole team and community behind it making it better all the time while your code just gets stale (I'm not saying it is, by the way - it's just an example).

From a personal point of view, knowing nHibernate is a transferable skill. Knowing CompanyXORM isn't.

like image 10
Fenton Avatar answered Nov 02 '22 17:11

Fenton