Skip to main content

N-Tier Architecture Design Using MVC, Entity Framework and WCF




 











Comments

  1. Hi, nice description about N-Tier Architecture Design Using MVC, Entity Framework and WCF .Thanks for your help..

    -Aparna
    Theosoft

    ReplyDelete

Post a Comment

Popular posts from this blog

Evolution of .NET Frame work

          Microsoft .Net technology has a rapid development and great success over the years. This is one of the best development platforms and accepted by all levels of peoples. The features like interoperability, security, portability, simplicity and maintainability makes the .NET technology as great. The .Net framework created on the year 2002 and still the features added and various versions of framework released for advanced software development. What is .Net Framework?           The .NET Framework is an integral Windows component that supports building and running the next generation of applications and XML Web services. The .NET Framework is designed to fulfill the following objectives: To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely. To provide a code-execution environment that minimizes software deployment and versioning conflicts. To

MVC or Web Forms

I.          I think both technologies can get a bit complicated after getting past any of the basics. Here are some brief opinions that I gathered while having to implement a project that must live in both MVC and WebForms hosts. WebForms Positives: The maturity of the product Lots of 3rd party support with regard to sophisticated controls There are ways to get around the legacy-feeling aspects of the framework (e.g., WebForms MVP ) WebForms Negatives: Page lifecycle issues can anger you to no end; there are a lot of moving parts to a sophisticated web application Using dependency injection is "difficult" to use/implement There is a lot in the framework that you can't control Need something like Reflector to dive into decompiled source when have questions that are not answered by documentation, web, experimentation. MVC Positives: Great separation of concerns and support of dependency injectio