* Updating System.IdentityModel.Tokens.Jwt and its dependencies in Orchard.Azure.MediaServices
* Using System.IO.Compression instead of DotNetZip
* Upgrading Newtonsoft.Json from 12.0.3 (vulnerable) to 13.0.3
* Updating ModuleRootWebConfig.txt codegen template according to the new Newtonsoft.Json version
* 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
#20590: Bugfix
#20590: Base Class Shape is Required
#20590: Formatting and file name comparison with OrdinalIgnoreCase
#20590: Removing base class Shape
#20590: Using Current instead of GetSetting
#20590: Updating comment
#20590: Migration Bugfix
#20590: Undoing rename
#20590: Removing extra whitespace in driver
#20590 Rename ShowFileNameEditor to FileNameEditor, Driver improvement, Updated Migration for MediaLibrary
Conflicts:
src/Orchard.Web/Modules/Orchard.MediaLibrary/Migrations.cs
#20590 Bugfix
#20590 Improving File Name editors display
#20590: Notifier Message Fix
#20590: Functionality to rename a media item
Work Item: 20590
Conflicts:
src/Orchard.Web/Modules/Orchard.MediaLibrary/Migrations.cs
src/Orchard.Web/Modules/Orchard.MediaLibrary/Orchard.MediaLibrary.csproj
Conflicts:
src/Orchard.Web/Modules/Orchard.MediaLibrary/Orchard.MediaLibrary.csproj
- Removed dependency on Orchard.Taxonomies
- Removed dependency on Orchard.Media
You will need to remove the Orchard_MediaLibrary tables and also
the Data Migration record corresponding to this module if you want to upgrade
from 1.x. You can also apply the database changes by hand, remove all the
records then use the Upgrade module to import all media.
--HG--
branch : 1.x
extra : rebase_source : 46100428d9546c3082bf65ce85d8d891543dc0a9
