What is loosely coupled and tightly coupled in MVC?

Hi,

 

 

Essentially, coupling is how much a given object or set of object relies on another object or another set of objects in order to accomplish its task.

 

Think of a car. In order for the engine to start, a key must be inserted into the ignition, turned, gasoline must be present, a spark must occur, pistons must fire, and the engine must come alive. You could say that a car engine is highly coupled to several other objects. This is high coupling, but it's not really a bad thing.

 

 

Think of a user control for a web page that is responsible for allowing users to post, edit, and view some type of information. The single control could be used to let a user post a new piece of information or edit a new piece of information. The control should be able to be shared between two different paths - new and edit. If the control is written in such a way that it needs some type of data from the pages that will contain it, then you could say it's too highly coupled. The control should not need anything from its container page.

 

You can follow the below link

http://www.c-sharpcorner.com/UploadFile/yusufkaratoprak/difference-between-loose-coupling-and-tight-coupling/

 

Thanks

Hi,

 

Denys Answer In Stack :

 

Loose coupling is simply writing software in such a way that all your classes can work independently without relying on each other. Since you're studying MVC I'll use it as an example to demonstrate the concept of loose coupling:

 

1) Tight coupling

 

ASP.NET Web forms are tightly coupled. Each .aspx page is dependent on it's code behind page which makes automated testing a nightmare

 

2) Loose coupling

 

ASP.NET MVC is loosely coupled.The logic is separated into 3 parts:

Please check the following reference :

 

http://tutlane.com/tutorial/aspnet-mvc/tightly-coupled-view-model-bounded-view-in-asp-net-mvc

https://stackoverflow.com/questions/15652861/what-is-loose-coupling