List of .NET libraries and frameworks

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

This article contains a list of notable libraries that can be used in .NET languages. While the .NET framework provides a basis for application development, which provides platform independence, language interoperability and extensive framework libraries, the development ecosystem around .NET is dependent on user libraries that are developed independently of the framework.

Standard Libraries (CLI) (including the Base Class Library (BCL)) are not included in this article because they have a separate article.

Application development in .NET Framework[edit]

Programs written for .NET Framework execute in a software environment known as Common Language Runtime (CLR), an application virtual machine that provides services such as security, memory management, and exception handling. Framework includes a large class library called Framework Class Library (FCL), which together with CLR constitute the .NET framework.

Thanks to the hosting virtual machine, different .NET CLI compliant languages can operate on the same kind of data structures. Therefore, all CLI compliant languages can use the Framework Class Library and other .NET libraries that are written in one of the CLI compliant languages. When source code of a CLI compliant language is compiled, the compiler generates a platform independent code in the Common Intermediate Language (also referred to as bytecode), which is stored in CLI assemblies. When a .NET application is executed, the just-in-time compiler (JIT) turns the CIL code into platform specific machine code. To improve performance, the .NET Framework also comes with Native Image Generator (NGEN), which performs ahead-of-time compilation to machine code.

This architecture has several implications. The framework provides language interoperability (each language can use code written in other languages) across the .NET CLI compliant languages programming languages. Calls from one language to another are exactly the same as would be within a single programming language. If a library is written in one CLI language, it can be used in any other CLI language. Moreover, applications that consist only of pure .NET assemblies, can be transferred to any platform that contains implementation of .NET framework and executed on that platform. For example, an application written for Microsoft .NET on Windows can also be executed on Mono (a cross platform alternative implementation of .NET) on Linux or macOS. Such applications are automatically cross-platform (or platform independent) to the extent to which the .NET framework itself is ported to different platforms.

Ability to transfer applications across platforms is extremely important for software developers, because in this way they can use the same code base for the application on any platform, enabling code reuse and avoiding code duplication. Both lead to reduced development and maintenance costs.

However, platform independence is only guaranteed in the described way when none of the assemblies constituting an application depends on any code that is not pure .NET code. Many .NET libraries, however, make use of native libraries (written e.g. in C or C++) or system calls through interoperability mechanisms such as COM interoperability and the P/Invoke feature, which makes possible to call native code and thus call into libraries written in compiled languages (as opposed to managed) such as C or C++.

In these cases, platform independence of applications written for the .NET framework also depends on the ability to transfer non-.NET libraries, on which application depends, to target platforms. Any additional such library may add significantly to the effort necessary to transfer the application to other platforms. Sometimes, the best solution is to re-implement the parts of application that depend on such a library for each targeted platform. In many cases, the vast majority of the application's code base can be easily transferred across platforms, and only small specific portions of code dependent on problematic libraries must be re-implemented for each platform. Sometimes, a special compatibility layer is introduced that provides a uniform API to the platform dependent parts of code. Then, even if the higher level code heavily depends on platform dependent parts, dependence is resolved through API calls that are the same on all platforms, and the same high level code can still be used on different target platforms.

A notable example is the Windows Forms graphical (GUI) class library. The library provides access to Windows User Interface Common Controls by wrapping the Windows API in managed code.[1] The library is therefore not easily transferred to platforms other than Windows. In spite of that, the cross-platform .NET implementation Mono implements the library. Because of that, an application that depends on Windows Forms, can be ported to other forms by using the Mono runtime on which the Windows Forms library is implemented (beside Windows, this includes Unix and OSX). The Mono's implementation of the library is written in C# in order to avoid Windows dependence.[2] Most of the Windows Forms API works on Mono, except for some minor incompatibilities and implementation bugs. However, many .NET libraries that were written on Windows and depend on Windows Forms, also make direct P/Invoke calls straight to the Windows API and bypass the Windows Forms API (this is sometimes done to avoid limitations of the Windows Forms). Such libraries will be broken when transferred to platforms other than Windows, although Windows Forms itself is available on these platforms via Mono implementation. For a GUI class library, the Mono project endorses use of the GTK# library,[citation needed] which is a .NET binding for the Gtk+ toolkit written in C.

GUI libraries are not the only critical area of interest for .NET developers. Other libraries that may be problematic include 3D graphics libraries, sound and video libraries and device dependent libraries in general. While some areas are very well covered by core .NET libraries (such as database connectivity, file I/O, sockets, HTTP, XML manipulation, standard cryptography), the others (such as numerical libraries, general parsing libraries) are easy to implement in pure .NET but may be under represented as compared to availability of corresponding native libraries. For developers of both proprietary and open source software (including free software), licensing information is also critically important. Entries in the list therefore provide information about the scope of the listed libraries, main dependencies (especially when these affect platform dependence), and licensing information.

Historical background[edit]

The .NET Framework has long supported cross-platform software development. The framework has been designed from the beginning for language interoperability, and parts of it were standardized in open standard (The Common Language Infrastructure and framework's most used programming language, C#). The original framework was first implemented only on Windows operating systems. Microsoft, the framework developer, and its partners, were working towards making their patents that cover some .NET - implemented technologies essential for framework implementation, available under "reasonable and non-discriminatory terms", which evolved into several patent promises issued by Microsoft. This made alternative third party implementations of the framework possible such as Mono, Portable.NET, and emulation CrossNet.[3]

In spite of that, it has long been a concern within the Open source community that using alternative .NET implementations for cross-platform development, especially of free software, is unsafe because of the possibility of Microsoft patent claims against such implementations. The Free Software Foundation's Richard Stallman has openly opposed inclusion of C# implementations in the default installation of GNU/Linux distributions and stated that they (the community) should discourage people from writing programs in C#. Primary concerns were parts of the framework implementations that were not subject to standards and were not explicitly included in Microsoft's patent promises.

The 2010s saw some significant shifts in Microsoft's approach towards the Open software community. The company open sourced the .NET Compiler Platform ("Roslyn") and the ASP.NET in April 2014, and later the .NET Core (open sourced on November 2014[4]) and other software. In February 2016, Microsoft acquired Xamarin, developer of Mono, an open source and cross platform implementation of .NET. On March 31, 2016 Microsoft announced at Microsoft Build that they will completely re-license Mono under the MIT license.[5] Microsoft issued the Patent Promise for Mono stating that they won't assert any "applicable patents" against parties that are "using, selling, offering for sale, importing, or distributing Mono".[6][7] It was also announced that the Mono Project was contributed to the .NET Foundation, a nonprofit organization established by Microsoft in March 2014 to improve open-source software development and collaboration around the .NET Framework.[8]

In light of these developments, a strong open source community has begun to develop around the .NET framework (especially on GitHub), starting a number of libraries and software projects[9] targeting the .NET framework for its cross platform character.

Libraries and frameworks[edit]

This section lists a number of notable .NET libraries (both open source and proprietary) arranged by topics.

.NET implementations[edit]

There are four primary .NET implementations that are actively developed and maintained:

.NET Standard
The .NET Standard is a set of APIs that are implemented per the Base Class Library of any .NET implementation. A library can target a version of the .NET Standard (rather than an implementation) and then it could be used (without recompiling) by any implementation that supports that level of the standard. This enables portability across different .NET implementations.
Implementation .NET Standard Versions[10][11]
1.0 1.1 1.2 1.3 1.4 1.5 1.6 2.0 2.1
.NET Core 1.0 1.0 1.0 1.0 1.0 1.0 1.0 2.0 3.0
.NET Framework 4.5 4.5 4.5.1 4.6 4.6.1 4.6.1 4.6.1 4.6.1 N/A[notes 1][12]
Mono 4.6 4.6 4.6 4.6 4.6 4.6 4.6 5.4 6.2
Xamarin.iOS 10.0 10.0 10.0 10.0 10.0 10.0 10.0 10.14 12.12
Xamarin.Mac 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.8 5.12
Xamarin.Android 7.0 7.0 7.0 7.0 7.0 7.0 7.0 8.0 9.3
Universal Windows Platform 10.0 10.0 10.0 10.0 10.0 10.0.16299 10.0.16299 10.0.16299 TBD
Windows (8) 8.0 8.0 8.1
Windows Phone 8.1 8.1 8.1
Windows Phone Silverlight 8.0
Unity 2018.1 2018.1 2018.1 2018.1 2018.1 2018.1 2018.1 2018.1 TBD

The table lists the minimum supported implementation version for each version of .NET Standard.

.NET Framework
the original .NET implementation that has existed since 2002.
an open source cross-platform implementation of .NET Framework. It runs on Linux, Mac OS, Android, and Windows.
.NET Core
a re-implementation of .NET Framework with the goal of making it cross-platform.
Universal Windows Platform (UWP)
an implementation of .NET used for building UWP apps. It's designed to unify development for different targeted types of devices, including PCs, tablets, phablets, phones, and the Xbox.

Each implementation of .NET includes the following components:

  • One or more runtimes. Examples are CLR for .NET Framework and CoreCLR for .NET Core.
  • A class library. Class library of each implementation must implements the .NET Standard, but may also implement additional APIs. Examples are .NET Framework Base Class Library and .NET Core Base Class Library.

Optionally, implementations can also include:

  • One or more application frameworks. Examples are ASP.NET (included in .NET Framework and .NET Core), Windows Forms (included in .NET Framework, Mono and in .NET Core since version 3.0), and Windows Presentation Foundation (WPF) (included in the .NET Framework and in the .NET Core since version 3.0).
  • Development tools. Some development tools are shared among multiple implementations. Examples are Visual Studio Code, .NET Software Development Kit (SDK), or NuGet.

Software frameworks[edit]

C# Native or csnative compiles C# code to machine code.
SharpLang compiles C# and other .NET languages to native machine code, using LLVM as a backend.
Cosmos is a C# Open Source Managed Operating System, an operating system "construction kit".
Fling OS
Fling OS is a C#-based operating system designed for learning low-level development.
MOSA Project
MOSA Project - Managed Operating System Alliance Project - a C# Operating System.

Web frameworks[edit]

a server-side web application framework designed for web development to produce dynamic web pages. It is the successor to Microsoft's Active Server Pages (ASP) technology built on the Common Language Runtime (CLR). It provides separate patterns for developing web applications ASP.NET MVC, ASP.NET Web API, and ASP.NET Web Pages (a platform using only Razor pages), which have merged into a unified MVC 6.[13]
a successor and re-implementation of ASP.NET as a modular web framework, together with other frameworks like Entity Framework. The framework uses the new open-source .NET Compiler Platform (codename "Roslyn") and is cross platform.
a web UI framework based on C#, Razor, and HTML that runs in the web browsers via WebAssembly. Blazor was designed to simplify the task of building fast single-page applications that run in any browser. It enables web developers to write .NET-based web apps that run client-side in web browsers using open web standards.
a web framework for programming interactive user interfaces written in C# that run in a web browser. Ooui can target WebAssembly (WASM), enabling Xamarin.Forms applications to be deployed in WASM and run in-browser without the need for a server-side scripting.[14]

Logging frameworks[edit]

one of the oldest logging libraries and frameworks for .NET. It was created as port of the Java framework log4j, and development later continued under the Apache Logging Services project. The library pioneered development of standard logging concepts such as log levels, loggers and appenders. It is released under the Apache License 2.0. At the current stage, log4net is a stable and mature library with a slow release cycle.[15][16]
a .NET open-source logging framework that was first released in 2006. It is being actively developed and is released under the BSD License.[15]
an open-source .NET logging library created in 2013. It is distinguished by supporting true structured logging (beyond just transforming an object value to text) out of the box. It is released under the Apache License 2.0.[15]

Numerical libraries[edit]

Open-source numerical libraries[edit]

a computer vision and artificial intelligence library. It implements a number of genetic, fuzzy logic and machine learning algorithms with several architectures of artificial neural networks with corresponding training algorithms.
a cross-platform open source numerical analysis and data processing library. It consists of algorithm collections written in different programming languages (C++, C#, FreePascal, Delphi, VBA) and has dual licensing - commercial and GPL.
an automatic differentiation library for exact and efficient calculation of derivatives. It includes symbolic and numerical differentiation. Released under GPLv3.[17]
a lightweight linear algebra library that supports generic types, implemented in F#. Released under the BSD License.[17]
IMSL Numerical Libraries for .NET
a commercial library of mathematical, statistical, data mining, financial and charting classes written in C#.
a GPL-licensed artificial neural network library entirely written in C#. Because it only depends on the core .NET assemblies, it is easily portable across platforms.
a large collection of numerical algorithms by Numerical Method Inc., which includes linear algebra, (advanced) optimization, interpolation, Markov model, principal component analysis, time series analysis, hypothesis testing, regressions, statistics, ordinary and partial differential equation solvers.
Math.NET Numerics
aims to provide methods and algorithms for numerical computations in science, engineering and every day use. Covered topics include special functions, linear algebra, probability models, random numbers, interpolation, integral transforms and more. MIT/X11 license.[17]
is a library for advanced scientific computation in the .NET Framework.
a collection of mathematical and statistical routines.
a generic linear algebra toolkit in C# compatible with Silverlight.

Proprietary numerical libraries[edit]

Alea GPU
a framework for developing GPU-accelerated algorithms in F# on .NET and Mono.[17]
a commercial high performance, typesafe numerical array classes and functions for general math, FFT and linear algebra, aims .NET/mono, 32&64 bit, script-like syntax in C#, 2D & 3D plot controls, efficient memory management. Released under GPLv3 or commercial license.[17]
Measurement Studio
a commercial integrated suite UI controls and class libraries for use in developing test and measurement applications. The analysis class libraries provide various digital signal processing, signal filtering, signal generation, peak detection, and other general mathematical functionality.
Microsoft Solver Foundation
a .NET package for designing and optimizing mathematical models.[17]
Commercial numerical component libraries for the .NET platform by CenterSpace Software, including signal processing (FFT) classes, a linear algebra (LAPACK & BLAS) framework, and a statistics package.[17]
Extreme Optimization Numerical Libraries
a commercial collection of mathematical and statistical classes for Microsoft .NET. It includes a large selection of standard algorithms from matrix factorization, function optimization, numerical integration, K-means clustering, and principal component analysis (PCA).[17]
a large collection of numerical algorithms by Numerical Method Inc., which includes linear algebra, (advanced) optimization, interpolation, Markov model, principal component analysis, time series analysis, hypothesis testing, regressions, statistics, ordinary and partial differential equation solvers.

2D graphics[edit]

Open-source 2D graphics libraries[edit]

a free, open source and cross platform charting library for .NET, released under the 3-clause-BSD license. Library includes classes for adding graphs to Windows Forms and ASP.NET, or to generate bitmaps.[18]
a cross-platform charting library for .NET and supports WinForms, WPF, Xamarin and UWP platforms, released under the MIT license.[19]
a web control for creating charts that render as images(png, jpg, gif, etc.).[20]
a .NET 2D charting library for drawing line, bar, and pie Charts, released under the LGPL license. Library provides a high degree of flexibility, where very many aspects of how graphs will be displayed can be configured.[21][22][23][24]

Proprietary 2D graphics libraries[edit]

Manufaktura Controls
a set of libraries for drawing music scores in desktop, mobile and web applications.

3D graphics[edit]

Open-source 3D graphics libraries[edit]

consists of C# wrappers around the VTK library. The source code is released under the BSD license.[25]
adds real-time 3D graphics; can be built for multiple platforms. Blotch3D sits on top of MonoGame and retains all its features. It is released under the Microsoft Public License.
Helix Toolkit
a 3D graphics toolkit that builds on and extends 3D capabilities of the WPF. Due to its dependence on WPF, the toolkit is limited to Windows platforms. It is released under the MIT license.[26][27][28]
free software used by game developers to make their Windows and Windows Phone games run on other systems. It currently supports OS X, Linux, iOS, Android, PlayStation Mobile, and the OUYA console. On Microsoft platforms it uses SharpDX and DirectX.[29] When targeting non-Microsoft platforms, platform specific capabilities are utilized by the OpenTK library. It is released under the Microsoft Public License.
Open Toolkit (OpenTK)
a low-level C# binding for OpenGL, OpenGL ES and OpenAL. It runs on Windows, Linux, Mac OS X, BSD, Android and iOS. It can be used standalone or integrated into a GUI.
Windows Presentation Foundation (WPF)
is a graphical subsystem for rendering user interfaces, developed by Microsoft. It also contains a 3D rendering engine. In addition, interactive 2D content can be overlaid on 3D surfaces natively.[30][31] It only runs on Windows operating systems.
LibVLCSharp is a cross-platform audio and video API for .NET platforms based on VideoLAN's LibVLC Library. It provides a comprehensive multimedia API that can be used across mobile, server and desktop to render video and output audio as well as encode and stream. It works on Android, iOS, Windows, Mac and Linux.

Proprietary 3D graphics libraries[edit]

a framework for .NET 3D with cameras, 3D models, 3D lines, 3D text and more.
a pure C#, 100% managed Vector Graphics Library. It has integration with GUI systems and Mobile platforms.
a cross-platform game engine developed by Unity Technologies[32] and used to develop video games for PC, consoles, mobile devices and websites.

Image processing[edit]

a computer vision and artificial intelligence library.[33][34] It implements a number of image processing algorithms and filters. It is released under the LGPLv3 and partly GPLv3 license. Majority of the library is written in C# and thus cross-platform.[citation needed] Functionality of AForge.NET has been extended by the Accord.NET library.[35][36]
another computer vision and artificial intelligence library, available under the Gnu Lesser General Public License, version 2.1. It is mainly written in C#.

Graphical user interface frameworks[edit]

Open-source GUI frameworks[edit]

a cross-platform XAML-based user interface (UI) framework. It has been inspired by Microsoft's Windows Presentation Foundation (WPF) (which was codenamed Avalon at an early development stage), and beside XAML for definition of widget controls it also features flexible CSS - like styling system (unlike the WPF's styling where styles are stored in the "Resources" collection). It supports the following operating systems: Windows (.NET Framework, .NET Core), Linux (GTK), MacOS, Android and iOS. It is released under the MIT license. Avalonia is currently in beta stage.[37][38]
a cross-platform desktop and mobile user interface framework released under the BSD license.[39][38]
C# wrappers around the underlying GTK+ and GNOME libraries, written in C and available on Linux, MacOS and Windows.[38]
C# bindings for the Qt framework.[38]
Uno Platform
an open source cross-platform graphical user interface for building applications that allow Universal Windows Platform - based code to run on iOS, Android, and WebAssembly.[40]
Platform is released under the Apache 2.0 license.
Windows Forms
a Microsoft's GUI framework. The original Microsoft implementation runs on Windows operating systems and provides access to Windows User Interface Common Controls by wrapping the Windows API in managed code.[1] The alternative Mono's implementation is open source and cross-platform (it runs on Windows, Linux, Unix and OS X). It is mainly compatible with the original implementation but not completely. The library is written in C# in order to avoid Windows dependence.[2]
At the Microsoft Connect event on December 4, 2018, Microsoft announced releasing of Windows Forms as open source project on GitHub. It is released under the MIT License. Windows Forms has become available for projects targeting the .NET Core framework. However, the framework is still available only on Windows platform and the Mono's incomplete implementation of WinForms remains the only cross-platform implementation.[41][42]
Windows Presentation Foundation
a graphical subsystem for rendering user interfaces in Windows-based applications by Microsoft. It is based on DirectX and employs XAML, an XML-based language, to define and link various interface elements.[43] WPF applications can be deployed as standalone desktop programs or hosted as an embedded object in a website.[citation needed]
At the Microsoft Connect event on December 4, 2018, Microsoft announced releasing of WPF as open source project on GitHub. It is released under the MIT License. Windows Presentation Foundation has become available for projects targeting the .NET Core framework. However, the system is still available only on Windows platform.[41][42]
The Windows UI Library (WinUI)
a set of Microsoft UI controls and features for the Universal Windows Platform (UWP). At the Microsoft Connect event on December 4, 2018, Microsoft announced releasing of WinUI as open source project on GitHub. WinUI has become available for projects targeting the .NET Core framework. It is released under the MIT License. However, the library is still available only on Windows platform.[41][42]
a GUI toolkit that maps API calls to native platform calls of the underlying platform, exposing one unified API across different platforms and making possible for the graphical user interfaces to have native look and feel on different platforms.[38]

Proprietary GUI frameworks[edit]

a cross-platform UI toolkit for development of native user interfaces that can be run on iOS, Android, and Universal Windows Platform apps. [44][45][38]

Security and identity management[edit]

Security headers for ASP.NET apps.
a tool for developers and/or administrators to manage the identity information for users of their applications
a free, open source OpenID Connect and OAuth 2.0 framework for ASP.NET Core
Serial Key Generating Library (SKGL)
a very simple licensing system that might be used to protect .NET Apps
client-side library for SSH, SCP and SFTP. It does not contain third party dependencies and is released under the BSD License.

Quality assurance[edit]

a random testing framework for testing .NET programs automatically. It is a port of Haskell's QuickCheck.
an open source unit testing framework for .NET, written in C# and thus cross-platform. It is one of many programs in the xUnit family. Licensed under MIT License.
Microsoft Unit Testing Framework
part of Visual Studio, only available on Windows platforms.

Object-relational mapping[edit]

.NET Framework natively provides utilities for object-relational mapping[46] through ADO.NET, a part of .NET stack since .NET 1.0. In addition, a number of third-party object-relational libraries have emerged, especially in earlier years of the .NET development, in order to fill some perceived gaps of the framework.[47][48][49]

As the framework has evolved, additional object-relational tools were added, such as the Entity Framework included with the .NET Framework 3.5. LINQ to SQL was also introduced with .NET 3.5. This somehow reduced significance and popularity of third-party object-relational libraries.

Open source object-relational mapping tools[edit]

Entity Framework
an open source[50] object-relational mapping (ORM) framework for ADO.NET. It was a part of .NET Framework, but since Entity framework version 6 it is separated from .NET framework.
NConstruct Lite
a desktop and web rapid application development tool and environment for .NET Framework, containing an extensive library for ORM.[51]
NHibernate is an object-relational mapper for the .NET platform.
an ORM-like-tool for F# language and SQL databases.

Proprietary object-relational mapping tools[edit]

an object-relational mapper and business logic layer development framework for .NET projects. The framework focuses on non-trivial domain models with deep inheritance and composite objects, and on code-first, test-driven development. It is a proprietary library that comes with source code, and community edition of the library is available for free.

Serialization and data formats[edit]

.NET Framework comes with a wide set of utilities for serialization of objects. The framework provides native object serialization to and from XML, JSON and binary streams. In spite of that, there are numerous third-party libraries that support serialization to target formats and working with these formats.

a JSON framework for the .NET platform. Beside serialization and deserialization of arbitrary objects, it features numerous utilities for working with JSON documents. One can compose the object structures that map to JSON documents, save them to strings, streams or files, reload object structures from streams, traverse the structures, find parts by using JSON Path (an analogue to XPath in XML), convert JSON documents to XML documents, etc.

See also[edit]



  1. ^ a b "C# 4.0 Unleashed By Bart De Smet. Sams Publishing, Jan 4, 2011 Chapter 5".
  2. ^ a b "GUI Toolkits". Mono site. 21 April 2016. Archived from the original on 2016-04-02. Retrieved 2016-04-21.
  3. ^ "CrossNet". Retrieved 17 April 2012.
  4. ^ Landwerth, Immo (12 November 2014). ".NET Core is Open Source". .NET Framework Blog. Microsoft. Retrieved 30 December 2014.
  5. ^ Anderson, Tim (31 March 2016). "Microsoft to make Xamarin tools and code free and open source". The Register.
  6. ^ Ferraira, Bruno (31 March 2016). "Xamarin now comes free with Visual Studio". The Tech Report.
  7. ^ "Microsoft Patent Promise for Mono". Mono on GitHub. Mono Project. 2016-03-28. Archived from the original on 2016-04-16. Retrieved 16 April 2016.
  8. ^ Lardinois, Frederic (April 3, 2014). "Microsoft Launches .NET Foundation To Foster The .NET Open Source Ecosystem". TechCrunch.
  9. ^ ".NET Open Source Developer Projects". GitHub. 15 April 2015. Archived from the original on 2016-04-15. Retrieved 2016-04-15.
  10. ^ ".NET Standard".
  11. ^ "This repo is building the .NET Standard. Contribute to dotnet/standard development by creating an account on GitHub". .NET Foundation. 3 April 2019.
  12. ^ "Announcing .NET Standard 2.1". .NET Blog. 5 November 2018.
  13. ^ "Introduction to ASP.NET 5 — ASP.NET 0.0.1 documentation".
  14. ^ Jeff Martin (18 April 2018). "Running .NET in the Browser with Ooui". Archived from the original on 2018-11-26. Retrieved 2018-11-26.
  15. ^ a b c Timms, Simon (27 August 2018). "NLog vs log4net vs Serilog: Compare .NET Logging Frameworks". Developer Tips, Tricks & Resources. Stackify. Retrieved 2018-12-19.
  16. ^ Watson, Matt (9 February 2017). "Ultimate log4net Tutorial for .NET Logging – 14 Best Practices, Resources and Tips". Developer Tips, Tricks & Resources. Stackify. Retrieved 2018-12-19.
  17. ^ a b c d e f g h "Guide - Math and Statistics Programming with F#". Archived from the original on 2016-04-25. Retrieved 2016-04-25.
  18. ^ Lerflaten, Olav (25 July 2007). "ASP.NET Charting with NPlot". Archived from the original on 2016-04-23. Retrieved 2016-04-21.
  19. ^ Airdrop, Ocean (10 March 2018). "OxyPlot Charting Control". Ocean Airdrop. Retrieved 2018-10-26.
  20. ^ Mitchell, Scott (8 December 2004). "A Look at WebCharts, a Free .NET Charting Control". Archived from the original on 2016-04-23. Retrieved 2016-04-21.
  21. ^ "Project Summary at OpenHUB". Archived from the original on 2016-04-23. Retrieved 2016-04-21.
  22. ^ Anthony, Paul (12 November 2008). "28 useful graphing solutions for web developers". Retrieved 2016-04-21.
  23. ^ Cora, Mike. "ShadyStats: Visualizing Game Statistics using Hierarchical Parallel Coordinates. A scientific article using Zedgraph" (PDF). Archived from the original (PDF) on 2016-04-21. Retrieved 2016-04-21.
  24. ^ Roman, Lucian (May 2014). "Software Application for Assessment the Reliability of the Suspension System at Opel Cars and of Road Profiles. A scientific article using Zedgraph" (PDF). Fascicle of Management and Technological Engineering. Archived from the original (PDF) on 2016-04-23. Retrieved 2016-04-21.
  25. ^ Messier, Nicole (31 January 2011). "Kitware's ActiViz .NET Tool is Now Free and Open Source". Archived from the original on 2016-04-22. Retrieved 2016-04-21.
  26. ^ "Helix repository on GitHub". GitHub. Archived from the original on 2016-04-25. Retrieved 2016-04-25.
  27. ^ "Getting started with WPF 3D". GitHub. Archived from the original on 2016-04-25. Retrieved 2016-04-25.
  28. ^ "Helix Toolkit web site". GitHub. Archived from the original on 2016-04-25. Retrieved 2016-04-25.
  29. ^ Monogame at Build 2012 | Channel 9 Live at BUILD 2012 | Channel 9
  30. ^ Introducing Windows Presentation Foundation
  31. ^ "What's New in WPF 3.5? Here's Fifteen Cool Features..." Retrieved 2007-10-14.
  32. ^ Riccitiello, John (October 23, 2014). "John Riccitiello sets out to identify the engine of growth for Unity Technologies (interview)". VentureBeat (Interview). Interviewed by Dean Takahashi. Retrieved January 18, 2015.
  33. ^ S M Hassan Ahmed, Todd C Alexander, Georgios Anagnostopoulos (May 2015). "Real-time, Static and Dynamic Hand Gesture Recognition for Human-Computer Interaction". University of Miami. Archived from the original on 2018-11-26. Retrieved 2018-11-26.CS1 maint: Uses authors parameter (link)
  34. ^ Suraj Verma, Prashant Pillai, Yim-Fun Hu (2012). "Development of an eye-tracking control system using AForge.NET framework". Int. J. Intelligent Systems Technologies and Applications, Vol. 11. Inderscience Enterprises. Archived from the original on 2018-11-26. Retrieved 2018-11-26.CS1 maint: Uses authors parameter (link)
  35. ^ Souza, César (20 May 2010). "Accord.NET Framework – An extension to AForge.NET". Archived from the original on 2018-11-26. Retrieved 2018-11-26.
  36. ^ "Framework Modules". Accord.NET Framework documetation. Archived from the original on 2018-11-26. Retrieved 2018-11-26.
  37. ^ Hanselman, Scott (September 2017). "What would a cross-platform .NET UI Framework look like? Exploring Avalonia". Archived from the original on 2018-11-26. Retrieved 2018-11-26.
  38. ^ a b c d e f Lex Li. "The Story About .NET Cross Platform UI Frameworks". 3 July 2017. Archived from the original on 2018-11-26. Retrieved 2018-11-26.
  39. ^ Wade (19 March 2018). "Cross Platform WinForms (Kinda)". .NET Core Tutorials. Archived from the original on 2018-11-26. Retrieved 2018-11-26.
  40. ^ Billson, Alex (15 Jul 2018). "Cross Platform Mobile Apps with .NET and Uno". Retrieved 2019-01-20.
  41. ^ a b c Martin, Jeff (4 December 2018). "Microsoft Open Sources WPF, WinForms, and WinUI". InfoQ. Retrieved 2018-12-06.
  42. ^ a b c Hanselman, Scott (4 December 2018). "Announcing WPF, WinForms, and WinUI are going Open Source". Retrieved 2018-12-06.
  43. ^ MSDN.NET Development: WPF: XAML Overview
  44. ^ "Xamarin.Forms Quickstart". Microsoft Docs. Microsoft. Retrieved 2018-11-26.
  45. ^ Nathan Williams. "Xamarin.Forms is Much More Capable Than You Think". ArcTouch. Archived from the original on 2018-11-26. Retrieved 2018-11-26.
  46. ^ Ambler, Scott. "Mapping Objects to Relational Databases: O/R Mapping In Detail". Agile Data. Archived from the original on 2018-11-03. Retrieved 2018-11-03.
  47. ^ Maksimovic, Zoran (November 2, 2017). "Microsoft.NET O/R mapper: choose your own!". Archived from the original on 2018-11-03. Retrieved 2018-11-03.
  48. ^ "List of ORM's available for .NET". Bala.NET Tips. WordPress. February 28, 2014. Archived from the original on 2018-11-03. Retrieved 2018-11-03.
  49. ^ "Object Relational Tool Comparison Dot Net". WikiWikiWeb. April 10, 2014. Archived from the original on 2018-11-03. Retrieved 2018-11-03.
  50. ^ Krill, Paul (20 July 2012). "Microsoft open-sources Entity Framework". InfoWorld. Retrieved 24 July 2012.
  51. ^ "NConstruct Lite - Project summary on GitHub". GitHub. Archived from the original on 2016-05-28. Retrieved 2016-05-28.

External links[edit]


Numerical libraries:


Cite error: There are <ref group=notes> tags on this page, but the references will not show without a {{reflist|group=notes}} template (see the help page).