PeachPied.WordPress.AspNetCore
v6.0.1-rc-006Pre-release
net5.0
The whole of WordPress, compiled, packed and provided as an ASP.NET Core package. Does not require PHP, becomes a part of ASP.NET Core application. Usage: 1. Add a package reference to "Peachpied.WordPress.AspNetCore" (Pre-Release) 2. Add WordPress as middleware within "Configure" method: app.UseWordPress(); 3. Optionally configure WordPress settings in "ConfigureServices" method. See https://github.com/iolevel/wpdotnet-sdk for more details.
Published
Oct 3, 2022
4y ago
Total Downloads
49.5K
49,499
Install
dotnet add package PeachPied.WordPress.AspNetCore --version 6.0.1-rc-006
| Product | Versions |
|---|---|
| .NET |
Changes from Previous Version
v6.0.1-rc-005v6.0.1-rc-006
Added Frameworks
net5.0
Removed Frameworks
.NETStandard2.1
Added Dependencies
PeachPied.WordPress.DotNet(net5.0)
PeachPied.WordPress.DotNetBridge(net5.0)
PeachPied.WordPress.HotPlug(net5.0)
PeachPied.WordPress(net5.0)
Microsoft.AspNetCore.Rewrite(net5.0)
Microsoft.AspNetCore.StaticFiles(net5.0)
NuGet.Protocol.Core.v3(net5.0)
Peachpie.AspNetCore.Web(net5.0)
Peachpie.Compiler.Diagnostics(net5.0)
Removed Dependencies
PeachPied.WordPress.DotNet(.NETStandard2.1)
PeachPied.WordPress.DotNetBridge(.NETStandard2.1)
PeachPied.WordPress.HotPlug(.NETStandard2.1)
PeachPied.WordPress(.NETStandard2.1)
Microsoft.AspNetCore.Http.Abstractions(.NETStandard2.1)
Microsoft.AspNetCore.ResponseCaching(.NETStandard2.1)
Microsoft.AspNetCore.Rewrite(.NETStandard2.1)
Microsoft.AspNetCore.StaticFiles(.NETStandard2.1)
Microsoft.Extensions.Configuration.Binder(.NETStandard2.1)
Microsoft.Extensions.DependencyModel(.NETStandard2.1)
Microsoft.Extensions.FileProviders.Physical(.NETStandard2.1)
NuGet.Protocol.Core.v3(.NETStandard2.1)
Peachpie.AspNetCore.Web(.NETStandard2.1)
Peachpie.Compiler.Diagnostics(.NETStandard2.1)
Adoption Assessment
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
This version is marked prerelease. Validate its API and upgrade path before production use.Compatibility metadata lists 1 target framework; confirm the exact target used by your application.The published metadata declares 14 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.