StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Frameworks
  4. Frameworks
  5. .NET vs Durandal

.NET vs Durandal

OverviewDecisionsComparisonAlternatives

Overview

.NET
.NET
Stacks15.4K
Followers5.9K
Votes1.9K
GitHub Stars21.7K
Forks4.9K
Durandal
Durandal
Stacks31
Followers36
Votes20
GitHub Stars1.7K
Forks371

.NET vs Durandal: What are the differences?

  1. Language Compatibility: .NET is a framework that primarily works with C# language, while Durandal is focused on JavaScript. This difference in language compatibility impacts the development flexibility and the skill set required for developers to work on these platforms.

  2. Framework Type: .NET is a comprehensive framework developed by Microsoft for building various types of applications, including web, mobile, desktop, and cloud-based solutions. On the other hand, Durandal is a lightweight framework specifically designed for creating single-page applications (SPAs). This difference in framework type influences the project scope and architecture choices.

  3. Community Support: .NET has a massive community of developers and resources available due to its widespread adoption and backing by Microsoft. In contrast, Durandal, being a niche framework, may have a smaller community and fewer resources for developers seeking assistance or learning materials.

  4. Hosting Requirements: .NET applications are typically hosted on Windows servers, leveraging Microsoft technologies like IIS (Internet Information Services). Durandal, being a JavaScript framework, can be hosted on any platform that can serve static files, making it more versatile in hosting options.

  5. Data Handling: In .NET, data handling is often done through the Entity Framework, providing a robust ORM (Object-Relational Mapping) solution for data manipulation. Durandal, being a client-side framework, relies on RESTful APIs and other backend technologies for data handling, which can impact the development approach and architecture of applications.

  6. Execution Environment: .NET applications run on the server-side, processing logic and rendering before delivering the output to the client. In contrast, Durandal applications run on the client-side, handling logic and rendering within the user's browser, offering a more dynamic and responsive user experience.

In Summary, .NET and Durandal differ in language compatibility, framework type, community support, hosting requirements, data handling, and execution environment, impacting development flexibility, project scope, community resources, hosting options, data manipulation, and user experience.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on .NET, Durandal

Ing. Alvaro
Ing. Alvaro

Software Systems Engineer at Ripio

May 21, 2020

Decided

Decided to change all my stack to microsoft technologies for they behave just great together. It is very easy to set up and deploy projects using visual studio and azure. Visual studio is also an amazing IDE, if not the best, when used for C#, it allows you to work in every aspect of your software.

Visual studio templates for ASP.NET MVC are the best I've found compared to django, rails, laravel, and others.

524k views524k
Comments

Detailed Comparison

.NET
.NET
Durandal
Durandal

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

Durandal is a cross-device, cross-platform client framework written in JS and designed to make Single Page Applications (SPAs) easy to create and maintain.

Multiple languages: You can write .NET apps in C#, F#, or Visual Basic.; Cross Platform: Whether you're working in C#, F#, or Visual Basic, your code will run natively on any compatible OS.; Consistent API & Libraries: To extend functionality, Microsoft and others maintain a healthy package ecosystem built on .NET Standard.; Application models for web, mobile, games and more: You can build many types of apps with .NET. Some are cross-platform, and some target a specific OS or .NET implementation.; Choose your tools: The Visual Studio product family provides a great .NET development experience on Windows, Linux, and macOS. Or if you prefer, there are .NET command line tools and plugins.
JS & HTML modularity; Simple app lifecycle; Eventing, modals, message boxes, etc; Navigation & screen state management;Consistent async programming w/ promises; App bundling and optimization; Use any backend technology; Built on top of jQuery, Knockout & requireJS; Integrates with popular CSS libraries such as Bootstrap and Foundation; Make your own templatable and data-bindable widgets; Fully testable
Statistics
GitHub Stars
21.7K
GitHub Stars
1.7K
GitHub Forks
4.9K
GitHub Forks
371
Stacks
15.4K
Stacks
31
Followers
5.9K
Followers
36
Votes
1.9K
Votes
20
Pros & Cons
Pros
  • 273
    Tight integration with visual studio
  • 262
    Stable code
  • 191
    Great community
  • 184
    Reliable and strongly typed server side language.
  • 141
    Microsoft
Cons
  • 13
    C#
  • 12
    Too expensive to deploy and maintain
  • 8
    Microsoft itself
  • 8
    Microsoft dependable systems
  • 5
    Hard learning curve
Pros
  • 3
    UI components
  • 3
    Easy to learn
  • 2
    Easy to start
  • 2
    Works IE8 >
  • 2
    Javascript
Integrations
C#
C#
Microsoft Azure
Microsoft Azure
F#
F#
Xamarin
Xamarin
Visual Basic
Visual Basic
Bootstrap
Bootstrap
Foundation
Foundation

What are some alternatives to .NET, Durandal?

Node.js

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Rails

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

AngularJS

AngularJS

AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.

Django

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

ASP.NET Core

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

Vue.js

Vue.js

It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API.

Symfony

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Spring

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase