Is it bad practice to use JavaScript with Razor Syntax in MVC?

Hey everyone,

Today, One of the developers of my organization said "It is a bad practice to use JavaScript with Razor Syntax(c#) in Asp.Net MVC project."

This topic takes lots of discussions but didn't get to any final result. What do you say about it?

Here is the following code that I have used in my Asp.Net MVC Project.

//This is my view.cshtml page

@if (ViewBag.ResponseMessage != null)

{

string ResponseType = @String.IsNullOrEmpty(ViewBag.ResponseType) ? "info" : ViewBag.ResponseType;

string ResponseTitle = @String.IsNullOrEmpty(ViewBag.ResponseTitle) ? "" : ViewBag.ResponseTitle;

}

There are three types of Logic

1.Data transformation Logic (ex:-display dob as Age) :-

Many developers fetch DOB from database and in view only they convert it in age and display.Yes it is a damn bad practise.better is to define Age property in viewmodel and in the setter get age by DOB property.

2.Presentation Logic (ex:- if marks scored by a Student is less than 35% then display it in Red color)

Many developers writes presentation logic in view, it is also a damn bad practise. better is to define Color property in view model and set appropriate color in the setter.

3. Data Access Logic:- only Data Access layer.

4.Never use Viewbag unnecessarily, it does boxing and unboxing use viewmodels and stronly typed views.

Now , if you are using Javascript (Ajax) then there is nothing wrong in it, if you are manipulating UI dynamically then also there is nothing wrong but if you are manipulating UI based on models property value , then it is absolutely bullshit, never do this.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Sachin Singh5y ago
Accepted answer
There are three types of Logic
1.Data transformation Logic (ex:-display dob as Age) :-
Many developers fetch DOB from database and in view only they convert it in age and display.Yes it is a damn bad practise.better is to define Age property in viewmodel and in the setter get age by DOB property.
2.Presentation Logic (ex:- if marks scored by a Student is less than 35% then display it in Red color)
Many developers writes presentation logic in view, it is also a damn bad practise. better is to define Color property in view model and set appropriate color in the setter.
3. Data Access Logic:- only Data Access layer.
4.Never use Viewbag unnecessarily, it does boxing and unboxing use viewmodels and stronly typed views.

Now , if you are using Javascript (Ajax) then there is nothing wrong in it, if you are manipulating UI dynamically then also there is nothing wrong but if you are manipulating UI based on models property value , then it is absolutely bullshit, never do this.