AForge.Imaging
50 Alternatives to AForge.Imaging
Compare AForge.Imaging to these popular alternatives based on real-world usage and developer feedback.
Json.NET is a popular high-performance JSON framework for .NET.
5,397 stacks0 votes10 followers
Compare AForge.Imaging vs Newtonsoft.Json →
JQuery is a new kind of JavaScript Library. jQuery is a fast and concise JavaScript Library that simplifies HTML document traversing, event handling, animating, and Ajax interactions for rapid web development. jQuery is designed to change the way that you write JavaScript. NOTE: This package is maintained on behalf of the library owners by the NuGet Community Packages project at http://nugetpackages.codeplex.com/.
3,845 stacks0 votes84 followers
Compare AForge.Imaging vs jQuery →
XUnit.net is a developer testing framework, built to support Test Driven Development, with a design goal of extreme simplicity and alignment with framework features. Installing this package installs xunit.core, xunit.assert, and xunit.analyzers.
2,624 stacks0 votes2 followers
Compare AForge.Imaging vs xunit →
Visual Studio 2012+ Test Explorer runner for the xUnit.net framework. Capable of running xUnit.net v1.9.2 and v2.0+ tests. Supports .NET 2.0 or later, .NET Core 1.0 or later, and Universal Windows 10.0 or later.
2,556 stacks0 votes4 followers
Compare AForge.Imaging vs xunit.runner.visualstudio →
Moq is the most popular and friendly mocking framework for .NET.
2,326 stacks0 votes1 followers
Compare AForge.Imaging vs Moq →
This package adds support for formatting and content negotiation to System.Net.Http. It includes support for JSON, XML, and form URL encoded data.
1,541 stacks0 votes8 followers
Compare AForge.Imaging vs Microsoft.AspNet.WebApi.Client →
Simple .NET logging with fully-structured events.
1,512 stacks0 votes1 followers
Compare AForge.Imaging vs Serilog →
JSON configuration provider implementation for Microsoft.Extensions.Configuration.
1,410 stacks0 votes3 followers
Compare AForge.Imaging vs Microsoft.Extensions.Configuration.Json →
This package contains the Microsoft.Web.Infrastructure assembly that lets you dynamically register HTTP modules at run time.
1,343 stacks0 votes2 followers
Compare AForge.Imaging vs Microsoft.Web.Infrastructure →
This package contains the core runtime assemblies for ASP.NET Web API. This package is used by hosts of the ASP.NET Web API runtime. To host a Web API in IIS use the Microsoft.AspNet.WebApi.WebHost package. To host a Web API in your own process use the Microsoft.AspNet.WebApi.SelfHost package.
1,329 stacks0 votes7 followers
Compare AForge.Imaging vs Microsoft.AspNet.WebApi.Core →
A semver implementation in .Net based on the v2.0.0 of the spec found at http://semver.org/.
1,261 stacks0 votes1 followers
Compare AForge.Imaging vs semver →
Entity Framework is Microsoft's recommended data access technology for new applications.
1,224 stacks0 votes9 followers
Compare AForge.Imaging vs EntityFramework →
Swagger tools for documenting APIs built on ASP.NET Core.
1,223 stacks0 votes0 followers
Compare AForge.Imaging vs Swashbuckle.AspNetCore →
NUnit features a fluent assert syntax, parameterized, generic and theory tests and is user-extensible. This package includes the NUnit 3 framework assembly, which is referenced by your tests. You will need to install version 3 of the nunit3-console program or a third-party runner that supports NUnit 3 in order to execute tests. Runners intended for use with NUnit 2.x will not run NUnit 3 tests correctly. Supported platforms: - .NET Framework 3.5+ - .NET Standard 1.4+ - .NET Core.
1,217 stacks0 votes0 followers
Compare AForge.Imaging vs NUnit →
Razor is a markup syntax for adding server-side logic to web pages. This package contains the Razor parser and code generation infrastructure.
1,201 stacks0 votes17 followers
Compare AForge.Imaging vs Microsoft.AspNet.Razor →
A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style unit tests. Targets .NET Framework 4.5 and 4.7, as well as .NET Core 2.0, .NET Core 3.0, .NET Core 2.1, .NET Standard 1.3, 1.6, 2.0 and 2.1. Supports the unit test frameworks MSTest, MSTest2, Gallio, NUnit, XUnit, MBUnit, MSpec, and NSpec.
1,191 stacks0 votes9 followers
Compare AForge.Imaging vs FluentAssertions →
This is MSTest V2, the evolution of Microsoft's Test Framework. Supported platforms: - .NET 4.5.0+ - .NET Core 1.0+ (Universal Windows Apps 10+, DNX Core 5+) - ASP.NET Core 1.0+ To discover and execute tests install MSTest.TestAdapter. To discover and execute tests for project.json based projects install dotnet-test-mstest.
1,181 stacks0 votes6 followers
Compare AForge.Imaging vs MSTest.TestFramework →
Implementation of key-value pair based configuration for Microsoft.Extensions.Configuration. Includes the memory configuration provider.
1,173 stacks0 votes1 followers
Compare AForge.Imaging vs Microsoft.Extensions.Configuration →
ASP.NET MVC is a web framework that gives you a powerful, patterns-based way to build dynamic websites and Web APIs. ASP.NET MVC enables a clean separation of concerns and gives you full control over markup.
1,168 stacks0 votes42 followers
Compare AForge.Imaging vs Microsoft.AspNet.Mvc →
This package contains core runtime assemblies shared between ASP.NET MVC and ASP.NET Web Pages.
1,146 stacks0 votes4 followers
Compare AForge.Imaging vs Microsoft.AspNet.WebPages →
Environment variables configuration provider implementation for Microsoft.Extensions.Configuration.
1,130 stacks0 votes0 followers
Compare AForge.Imaging vs Microsoft.Extensions.Configuration.EnvironmentVariables →
Modernizr adds classes to the <html> element which allow you to target specific browser functionality in your stylesheet. You don't actually need to write any Javascript to use it. Modernizr is a small and simple JavaScript library that helps you take advantage of emerging web technologies (CSS3, HTML5) while still maintaining a fine level of control over older browsers that may not yet support these new technologies. NOTE: This package is maintained on behalf of the library owners by the NuGet Community Packages project at http://nugetpackages.codeplex.com/.
1,124 stacks0 votes12 followers
Compare AForge.Imaging vs Modernizr →
Logging infrastructure default implementation for Microsoft.Extensions.Logging.
1,115 stacks0 votes1 followers
Compare AForge.Imaging vs Microsoft.Extensions.Logging →
This package contains everything you need to host ASP.NET Web API on IIS. ASP.NET Web API is a framework that makes it easy to build HTTP services that reach a broad range of clients, including browsers and mobile devices. ASP.NET Web API is an ideal platform for building RESTful applications on the .NET Framework.
1,082 stacks0 votes1 followers
Compare AForge.Imaging vs Microsoft.AspNet.WebApi.WebHost →
A package including the NUnit 3 TestAdapter for Visual Studio 2012 onwards. With this package you don't need to install the VSIX adapter package, and you don't need to upload the adapter to your TFS server. Note that this package ONLY contains the adapter, not the NUnit framework. You must also get the framework. For VS 2017 and forward, you should add this package to every test project in your solution. (Earlier versions only require a single adapter package per solution.) The package works with Visual Studio 2012 and newer.
1,068 stacks0 votes0 followers
Compare AForge.Imaging vs NUnit3TestAdapter →
A Serilog sink that writes log events to the console/terminal.
1,056 stacks0 votes0 followers
Compare AForge.Imaging vs Serilog.Sinks.Console →
Provides a programming interface for modern HTTP applications, including HTTP client components that allow applications to consume web services over HTTP and HTTP components that can be used by both clients and servers for parsing HTTP headers. Commonly Used Types: System.Net.Http.HttpResponseMessage System.Net.Http.DelegatingHandler System.Net.Http.HttpRequestException System.Net.Http.HttpClient System.Net.Http.MultipartContent System.Net.Http.Headers.HttpContentHeaders System.Net.Http.HttpClientHandler System.Net.Http.StreamContent System.Net.Http.FormUrlEncodedContent System.Net.Http.HttpMessageHandler When using NuGet 3.x this package requires at least version 3.4.
1,056 stacks0 votes1 followers
Compare AForge.Imaging vs System.Net.Http →
This package contains everything you need to host ASP.NET Web API on IIS. ASP.NET Web API is a framework that makes it easy to build HTTP services that reach a broad range of clients, including browsers and mobile devices. ASP.NET Web API is an ideal platform for building RESTful applications on the .NET Framework.
1,031 stacks0 votes10 followers
Compare AForge.Imaging vs Microsoft.AspNet.WebApi →
A convention-based object-object mapper.
1,005 stacks0 votes10 followers
Compare AForge.Imaging vs AutoMapper →
Includes types that provide support for creating, serializing and validating JSON Web Tokens.
984 stacks0 votes0 followers
Compare AForge.Imaging vs System.IdentityModel.Tokens.Jwt →
The Amazon Web Services SDK for .NET - Core Runtime.
941 stacks0 votes3 followers
Compare AForge.Imaging vs AWSSDK.Core →
Default implementation of dependency injection for Microsoft.Extensions.DependencyInjection.
926 stacks0 votes2 followers
Compare AForge.Imaging vs Microsoft.Extensions.DependencyInjection →
Log4net is a tool to help the programmer output log statements to a variety of output targets. In case of problems with an application, it is helpful to enable logging so that the problem can be located. With log4net it is possible to enable logging at runtime without modifying the application binary. The log4net package is designed so that log statements can remain in shipped code without incurring a high performance cost. It follows that the speed of logging (or rather not logging) is crucial. At the same time, log output can be so voluminous that it quickly becomes overwhelming. One of the distinctive features of log4net is the notion of hierarchical loggers. Using these loggers it is possible to selectively control which log statements are output at arbitrary granularity. log4net is designed with two distinct goals in mind: speed and flexibility.
926 stacks0 votes5 followers
Compare AForge.Imaging vs log4net →
Functionality to bind an object to data in configuration providers for Microsoft.Extensions.Configuration.
918 stacks0 votes0 followers
Compare AForge.Imaging vs Microsoft.Extensions.Configuration.Binder →
Web Grease is a suite of tools for optimizing javascript, css files and images.
906 stacks0 votes1 followers
Compare AForge.Imaging vs WebGrease →
ASP.NET Optimization introduces a way to bundle and optimize CSS and JavaScript files.
896 stacks0 votes0 followers
Compare AForge.Imaging vs Microsoft.AspNet.Web.Optimization →
Low-level Serilog provider for Microsoft.Extensions.Logging.
869 stacks0 votes0 followers
Compare AForge.Imaging vs Serilog.Extensions.Logging →
ANother Tool for Language Recognition, is a language tool that provides a framework for constructing recognizers, interpreters, compilers, and translators from grammatical descriptions containing actions in a variety of target languages.
859 stacks0 votes1 followers
Compare AForge.Imaging vs Antlr →
Provides a set of helper types and abstractions for simplifying the creation of OWIN components.
842 stacks0 votes0 followers
Compare AForge.Imaging vs Microsoft.Owin →
Abstractions for dependency injection. Commonly used types: Microsoft.Extensions.DependencyInjection.IServiceCollection.
828 stacks0 votes0 followers
Compare AForge.Imaging vs Microsoft.Extensions.DependencyInjection.Abstractions →
Amazon Simple Storage Service (Amazon S3), provides developers and IT teams with secure, durable, highly-scalable object storage.
806 stacks0 votes1 followers
Compare AForge.Imaging vs AWSSDK.S3 →
Entity Framework Core is a lightweight and extensible version of the popular Entity Framework data access technology. Commonly Used Types: Microsoft.EntityFrameworkCore.DbContext Microsoft.EntityFrameworkCore.DbSet.
795 stacks0 votes20 followers
Compare AForge.Imaging vs Microsoft.EntityFrameworkCore →
Logging abstractions for Microsoft.Extensions.Logging. Commonly used types: Microsoft.Extensions.Logging.ILogger Microsoft.Extensions.Logging.ILoggerFactory Microsoft.Extensions.Logging.ILogger<TCategoryName> Microsoft.Extensions.Logging.LogLevel Microsoft.Extensions.Logging.Logger<T> Microsoft.Extensions.Logging.LoggerMessage Microsoft.Extensions.Logging.Abstractions.NullLogger.
781 stacks0 votes0 followers
Compare AForge.Imaging vs Microsoft.Extensions.Logging.Abstractions →
Replacement CodeDOM providers that use the new .NET Compiler Platform ("Roslyn") compiler as a service APIs. This provides support for new language features in systems using CodeDOM (e.g. ASP.NET runtime compilation) as well as improving the compilation performance of these systems. This package was built from the source at https://github.com/aspnet/RoslynCodeDomProvider/commit/12975a5a1616dbefac02ba8113204b59cba7eeec.
778 stacks0 votes0 followers
Compare AForge.Imaging vs Microsoft.CodeDom.Providers.DotNetCompilerPlatform →
ASP.NET Core MVC features that use Newtonsoft.Json. Includes input and output formatters for JSON and JSON PATCH. This package was built from the source code at https://github.com/aspnet/AspNetCore/tree/e276c8174b8bfdeb70efceafa81c75f8badbc8db.
778 stacks0 votes1 followers
Compare AForge.Imaging vs Microsoft.AspNetCore.Mvc.NewtonsoftJson →
Provides additional types that simplify the work of writing concurrent and asynchronous code. Commonly Used Types: System.Threading.Tasks.ValueTask<TResult> 637a8d58f72f2b0f1a71187530c3cf433e95a75a.
771 stacks0 votes1 followers
Compare AForge.Imaging vs System.Threading.Tasks.Extensions →
Provides resource pooling of any type for performance-critical applications that allocate and deallocate objects frequently. Commonly Used Types: System.Buffers.ArrayPool<T> 30ab651fcb4354552bd4891619a0bdd81e0ebdbf When using NuGet 3.x this package requires at least version 3.4.
728 stacks0 votes0 followers
Compare AForge.Imaging vs System.Buffers →
Amazon Lambda .NET Core support - Core package.
721 stacks0 votes2 followers
Compare AForge.Imaging vs Amazon.Lambda.Core →