fb1aa73475
* Upgrading projects, code generation templates and Specflow app to use Microsoft.CodeDom.Providers.DotNetCompilerPlatform 4.1.0 (latest) * Updating csprojs not to define LangVersion separately in Release and Debug mode, setting it to "default" instead of "latest" * Restricting C# language version to 7.3 * Downgrading SmtpMessageChannel.cs to C# 7.3 * Setting MvcBuildViews = false in the remaining csprojs that reference DotNetCompilerPlatform, like the others * Setting RoslynCopyToOutDir = false in each csproj that references DotNetCompilerPlatform See https://github.com/aspnet/RoslynCodeDomProvider?tab=readme-ov-file#build-time-options - We only need Orchard.Web to include the Roslyn tools in its bin folder, the other csprojs only need the DLL reference - We could simply remove the targets import in these csprojs, but it will be re-added when the package is updated, so this is cleaner/easier * We don't actually need <MvcBuildViews>false</MvcBuildViews> in csprojs * Orchard.Web: Copying Roslyn files to the output folder using the provided target (CopyRoslynCompilerFilesToOutputDirectory) instead of our custom one * Orchard.proj: Factoring out a part of the Compile target into the DevCompile target and removing BuildViews target - For a simple local build (just to validate that the solution builds), we don't actually need that second build that copies files to the output folder. - CI builds (Test, Spec, etc.) that operate on the build output folder are unaffected, because Compile calls DevCompile - The BuildViews target is not really necessary, just call any other target (Compile, DevCompile, Spec, etc.) with "/p:MvcBuildViews=true" * Removing incorrect comment about Razor IntelliSense * Removing VBCodeProvider configuration from Web.config files * Getting rid of Microsoft.CodeDom.Providers.DotNetCompilerPlatform.targets imports and associated configuration except in Orchard.Web.csproj * Adding VB compiler configuration to src/Orchard.Web/Web.config, because it would be readded on rebuild by the imported target anyway |
||
|---|---|---|
| .github/workflows | ||
| lib | ||
| src | ||
| .deployment | ||
| .gitattributes | ||
| .gitignore | ||
| .hgeol | ||
| build.cmd | ||
| CalculateBindingRedirects.ps1 | ||
| CleanSolution.ps1 | ||
| ClickToBuild.cmd | ||
| ClickToBuildAzurePackage.cmd | ||
| CREDITS.txt | ||
| DeleteModuleBinaries.cmd | ||
| deploy.cmd | ||
| LICENSE.txt | ||
| Orchard.proj | ||
| README.md | ||
Orchard
Orchard is a free, open source, community-focused Content Management System built on the ASP.NET MVC platform.
You can try it for free on DotNest.com or on Microsoft Azure by clicking on this button.
About The Orchard Project
Please visit our website at https://orchardproject.net for the most current information about this project.
Orchard is a free, open source, community-focused Content Management System built on the ASP.NET MVC platform.
Orchard is built on a modern architecture that puts extensibility up-front, as its number one concern. All components in Orchard can be replaced or extended. Content is built from easily composable building blocks. Modules extend the system in a very decoupled fashion, where a commenting module for example can as easily apply to pages, blog posts, photos or products. A rich UI composition system completes the picture and ensures that you can get the exact presentation that you need for your content.
Orchard is delivered under the .NET Foundation. It is licensed under a New BSD license, which is approved by the OSI.
Our mission is to empower our users and foster a dedicated and diverse community that builds the CMS that we all want to use.
Project Status
Orchard is currently in version 1.10.3: It contains bugfixes and the more impactful changes and new features added in the latest major version (1.10).
We invite participation by the developer community in shaping the project’s direction, so that we can publicly validate our designs and development approach. All our releases are available on our Releases page, and we encourage interested developers to check out the source code on the Orchard GitHub site and get involved with the project.
How To Get Involved
We hope that by engaging with the community we will continue to shape Orchard into a valuable set of tools and applications. The Orchard team is committed to open community participation and accepts code contributions. We encourage community participation at all levels from general project feedback to bug fixes and patches.
There are many ways you can contribute to Orchard:
- Check out the code
- Write documentation
- Find and file a bug
- Propose a feature idea
- Ask and answer questions on Stack Overflow
- Participate in our gitter.im chatroom
- Submit a pull request
- Translate Orchard
- Contribute modules and themes to our gallery
The Future Of Orchard CMS: Orchard Core
As the underlying frameworks (.NET, ASP.NET and ASP.NET MVC) are constantly evolving, Orchard of course keeps track of the changes and improvements of these: Orchard Core is the next generation of Orchard releases that is based on ASP.NET Core. Just like the current Orchard project, it's fully open-source and is publicly available on GitHub. Orchard Core (as a framework) is being built from scratch: it's still in development and does not share any of its code base (at least directly) with the current versions (1.x) of Orchard.