---
title: "What is the concept of Tight Coupling in asp.net MVC?"
description: "What is the concept of Tight Coupling in asp.net MVC?"
author: "Kalin"
published: 2022-03-11
updated: 2023-06-04
canonical: https://www.mindstick.com/forum/156912/what-is-the-concept-of-tight-coupling-in-asp-dot-net-mvc
category: "asp.net mvc"
tags: ["asp.net", "asp.net mvc"]
reading_time: 4 minutes
---
# What is the concept of Tight Coupling in asp.net MVC?
What is the [concept](https://www.mindstick.com/blog/79/routing-concept-in-dot-net) of [Tight Coupling](https://www.mindstick.com/forum/155753/how-we-achieve-tight-coupling-view-in-asp-dot-net-mvc) in [asp.net MVC](https://www.mindstick.com/forum/155798/what-is-caching-in-asp-dot-net-mvc)?
## Replies
### Reply by Aryan Kumar
Tight coupling in ASP.NET MVC refers to the situation where the components of an application are highly interdependent. This can make the application difficult to maintain and update, as changes to one component can often require changes to other components.
There are a number of factors that can lead to tight coupling in ASP.NET MVC applications, including:
- **Using concrete classes in views:** When a view uses a concrete class, it is tightly coupled to that class. This is because the view will only work with that specific class, and any changes to the class will require changes to the view.
- **Using hard-coded values in views:** When a view uses hard-coded values, it is tightly coupled to those values. This is because the view will only work with those specific values, and any changes to the values will require changes to the view.
- **Using global variables:** When global variables are used in an application, they can lead to tight coupling. This is because any component that needs to access the variable will be tightly coupled to it.
There are a number of things that can be done to reduce tight coupling in ASP.NET MVC applications, including:
- **Using interfaces in views:** When a view uses an interface, it is not tightly coupled to any specific class. This is because the view can work with any class that implements the interface.
- **Using data binding in views:** Data binding can be used to decouple views from the data that they are displaying. This is because the view does not need to know anything about the data, it simply needs to know how to display it.
- **Using dependency injection:** Dependency injection can be used to decouple components from each other. This is done by injecting the dependencies that a component needs into it, rather than having the component find or create those dependencies itself.
By reducing tight coupling in ASP.NET MVC applications, developers can make their applications more maintainable and easier to update.
Here are some of the disadvantages of tight coupling:
- **Reduced flexibility:** Tightly coupled components are difficult to change or reuse. This can make it difficult to add new features or to change the way that an application works.
- **Increased complexity:** Tightly coupled components can make an application more complex to understand and to debug.
- **Reduced performance:** Tightly coupled components can reduce the performance of an application. This is because tightly coupled components often need to communicate with each other, which can add overhead.
If you are developing an ASP.NET MVC application, I recommend that you avoid tight coupling by using interfaces, data binding, and dependency injection. By doing this, you can make your application more maintainable, flexible, and performant.
### Reply by Steilla Mitchel
**Tight [Coupling](https://www.mindstick.com/forum/157700/explain-in-brief-about-cohesion-and-coupling-in-software-engineering) in [mvc](https://www.mindstick.com/forum/155803/define-cache-profile-in-mvc):**\
In [asp.net](https://www.mindstick.com/articles/934/default-folders-available-inside-the-asp-dot-net-application-folder) MVC model bounded view is a tight coupled means that model is used to create a view. Lets create a tight coupled view in asp.net mvc. **1- Create Model in asp.net mvc:**
```
Model file name is PersonData
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
namespace Mindstick.Models
{
public class PersonData
{
public int ID { get; set; }
public string Name { get; set; }
public string Address { get; set; }
}
}
```
**2- Create Controller:** Now lets create a controller page, Named PersonDataController. Here add an attribute [httpGet] to action method and return new instance model PersonData,
```
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Mindstick.Models;
namespace Mindstick.Controllers
{
public class PersonDataController : Controller
{// GET: /PersonData/
[HttpGet]
public ActionResult Index()
{
return View(new PersonData());
}
}
}
```
**3- Create View page:** **\** Lets create a view page, view file name Index, view engine - Razor (CSHTML) and model class is PersonData(Mindstick.Models).
```
@model Mindstick.Models.PersonData @{ViewBag.Title = 'Index';
}