We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

ASP.net MVC and ASP.net MVC(Classic)

Thread ID:

Created:

Updated:

Platform:

Replies:

121390 Dec 7,2015 07:50 PM Dec 16,2015 06:17 AM ASP.NET MVC 5
loading
Tags: General
Josef Szeliga
Asked On December 7, 2015 07:50 PM

 
 
I performed a search over the internet and except for Syncfusion no one else is refering to two seperate frameworks called ASP.net MVC and ASP.net MVC (Classic).
So this must be a purely Syncfusion thing.
So i searched Syncfusion forums and knowledge base for these two frameworks as to why they are different, how they are different. Why use one over the other.
And I get nothging, Nothing.
Where can i read up about them ? 
 
How are they different ? When to use one over the other ?
 
At the moment I have a project but have no idea which of these framework was used to create the project.
How can I tell without knowing which templates were used to create it ?
 
I'm getting missing namespaces. Have I mixed the two types in my code ?
Again, how can I tell ?
 
This shouldn't be an issue. I want to spend my type developing no dealing with issues introduced by Syncfusion marketing.
 

Varalakshmi R.S [Syncfusion]
Replied On December 8, 2015 05:58 AM


Hi Josef Szeliga,

Thanks for your interest in Syncfusion products.

Difference between ASP.NET MVC and ASP.NET MVC (classic)

The suite of ASP.NET MVC controls which was offered as “Essential Studio for ASP.NET MVC” till the Volume 4 2013 release has been marked as “Classic” and the newer set of controls powered by Essential JavaScript takes its place. The newer version provides several advantages over the classic edition including being purely client side rendered HTML5/JavaScript controls, offers better performance and provides better support for touch interactivity.

You can use our Essential Studio latest version Volume3, 2015 and it is available for download under the following location.

https://www.syncfusion.com/downloads/version-history/13_3_0_7

Advantages ASP.NET MVC over classic MVC are listed below.

·         ASP.NET MVC controls are completely built in client side.

·         Third party support like Angular JS, Knock out JS are included.

·         It is compatible with Bootstrap CSS.

·         It has clean mark up.

·         It has better performance over classic components.

·         It has clean UI

·         Theming support – we have provided thirteen variants, which includes both light and dark variations.

·         ASP.NET MVC controls are responsive. So we can run in both Desktop and devices

·         Touch support is enabled.

·         RTL support is included.

·         Provided with globalization support for all widgets.

·         UI interaction and appearance are best when compared to MVC (Classic).

ASP.NET MVC reference details

In order to get started with ASP.NET MVC components refer the below link which includes all the details to get started with ASP.NET MVC Components.

http://help.syncfusion.com/aspnetmvc/getting-started

online samples link: http://mvc.syncfusion.com/demos/web

ASP.NET MVC (classic) reference details

You can refer the following links to know more details about classic MVC controls.

http://help.syncfusion.com/aspnetmvc-classic/getting-started

online samples link: http://mvc.syncfusion.com/demos/ui/tools

I'm getting missing namespaces. Have I mixed the two types in my code ?

Again, how can I tell ?

Yes, both framework assemblies are referred in your sample application. Could you please go through the above details and confirm your platform and control details with us? So that we will be able to prepare a simple sample and share it with you.


Please let us know if you have any queries.

Regards,

Varalakshmi



Josef Szeliga
Replied On December 8, 2015 06:54 PM

Thank you.
I will stick with the MVC not the classic MVC.
It appears my control was an MVC Classic control and I have replaced it with

Html.EJ().Splitter

This allowed me to remove the classic MVC references in my config files.

As the EJ.MVC names space was already in the config files and the EJ.MVC assemblies already references the code works as expected

Thank you for your assistance.


Prasanth Palani [Syncfusion]
Replied On December 10, 2015 04:10 AM

Hi Josef,
 
Thanks for your update.
 
Please let us know, if you have further assistance. We will happy to help you.
 
Regards,
Prasanth P.

Alisasmith
Replied On December 15, 2015 06:39 AM

Hi Josef Szeliga,

From my knowledge, ASP.Net MVC is the latest version of ASP.net. It is a  lightweight framework for developing web applications using MVC( Model View Controller). The performance of MVC framework is much better than classic components.

For more detail, go through the following links :-
http://www.codeproject.com/Articles/38629/ASP-NET-MVC-or-Classic-ASP-NET-What-to-Choose
http://docs.sitefinity.com/for-developers-classic-mvc-mode

Manikandan Mariappan [Syncfusion]
Replied On December 16, 2015 06:17 AM

Hi Josef,
Thanks for sharing your general information.
In ASP.NET MVC, the Syncfusion provides new controls with several advantages over the classic edition including being purely client side rendered HTML5/JavaScript, offers better performance and provides better support for touch interactivity. 
The older version MVC components have marketed as ASP.NET MVC Classic.
If you want to know or need any details regarding our products. Please let us know we will happy to assist you.
Regards,
M.Manikandan

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;