Found 397 packages
NuGet's core types and interfaces for PackageReference-based restore, such as lock files, assets file and internal restore models.
Provides supporting infrastructure for portable projects: support identifiers that define framework and runtime for support targets and packages that reference the minimum supported package versions when targeting these. When using NuGet 3.x this package requires at least version 3.4.
Easily identify which dependencies can be removed from an MSBuild project.
Provides abstractions for reading `.deps` files. When a .NET application is compiled, the SDK generates a JSON manifest file (`<ApplicationName>.deps.json`) that contains information about application dependencies. You can use `Microsoft.Extensions.DependencyModel` to read information from this manifest at run time. This is useful when you want to dynamically compile code (for example, using Roslyn Emit API) referencing the same dependencies as your main application. By default, the dependency manifest contains information about the application's target framework and runtime dependencies. Set the PreserveCompilationContext project property to `true` to additionally include information about reference assemblies used during compilation.
Rewrites NuGet reference HintPath values at build-time for projects that exist in multiple solutions with different packages folders.
A community answer to Microsoft’s decision to single out net35 by excluding it from the https://www.nuget.org/packages/Microsoft.NETFramework.ReferenceAssemblies/ package. This package provides the .NET Framework 3.5 reference assemblies so that net35 projects can be built using the dotnet CLI. Example project that targets multiple frameworks: <Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFrameworks>net35;net40;netstandard2.0;netcoreapp3.0</TargetFrameworks> </PropertyGroup> <ItemGroup> <PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.0" /> <PackageReference Include="jnm2.ReferenceAssemblies.net35" Version="1.0.1" /> </ItemGroup> </Project>
Allows project reference content to be added to the NuGet-package during pack process.
This package provides build infrastructure components so that projects referencing specific Microsoft packages can successfully build. Do not directly reference this packages unless you receive a build warning that instructs you to add a reference.
Tool to auto-generate BCL package nuspec dependencies for CoreCLR projects
This package delivers a complete executable copy of MSBuild. Reference this package only if your application needs to load projects or execute in-process builds without requiring installation of MSBuild. Successfully evaluating projects using this package requires aggregating additional components (like the compilers) into an application directory.
Provides an integration with TeamCity for test frameworks. Usage: - Create a test project, for example using the command line: dotnet new xunit - Add the NuGet reference to this package
NLog Schema XSD-file for enabling Intellisense, when editing NLog.config XML file in Visual Studio. The nuget-package will try to copy the XSD-file into the project-folder, so one can reference NLog.xsd from NLog.config: <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.nlog-project.org/schemas/NLog.xsd NLog.xsd"> </nlog> If this nuget-package fails to place the XSD-file into the project-folder then one can download latest here: https://nlog-project.org/schemas/NLog.xsd Alternative enable the Visual Studio option "Automatically download DTDs and schemas" and specify the complete URL: <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.nlog-project.org/schemas/NLog.xsd http://www.nlog-project.org/schemas/NLog.xsd"> </nlog>
Package Description
Elastic APM .NET agent. This is a convenient package that automatically pulls in ASP.NET Core, and Entity Framework Core auto instrumentation with the Elastic APM .NET Agent. If your application uses the Microsoft.AspNetCore.All package the easiest way to reference the Elastic APM project is to use this package. If you only need specific functionalities (e.g. EF Core monitoring, or ASP.NET Core without EF Core monitoring, etc) you can reference specific Elastic.Apm packages. See: https://github.com/elastic/apm-agent-dotnet/tree/main/docs
.NET Spatial Reference and Projection Engine. Proj.NET performs point-to-point coordinate conversions between geodetic coordinate systems for use in fx. Geographic Information Systems (GIS) or GPS applications. The spatial reference model used adheres to the Simple Features specification.
This package includes analyzers and code fixes for test projects using NUnit 3+. The analyzers will mark wrong usages when writing tests, and the code fixes can be used to used to correct these usages. They will also aid in the transition from NUnit 3 to NUnit 4. Version 3.0 and upwards works in Visual Studio 2019 (version 16.3) or newer and also enables supression of compiler errors such as errors arising from nullable reference types. For Visual Studio 2017 one must use versions below 3.0 - note that these versions are no longer updated, so version 2.10.0 is the last version that works in Visual Studio 2017.
This package generates an API reference for the project it's added to, to allow easy API diffs.
A set of templates to use in combination with Crafters Reference Architecture.
This package has been deprecated. An update will remove the current use of this package from the project and replace it with a reference to the 'NServiceBus' nuget.