2015-12-15 19:55:23 +08:00
|
|
|
<?xml version="1.0" encoding="utf-8"?>
|
|
|
|
|
<packages>
|
2022-01-21 15:47:00 +08:00
|
|
|
<package id="Antlr3.Runtime" version="3.5.1" targetFramework="net48" />
|
2021-02-19 17:31:26 +08:00
|
|
|
<package id="Autofac" version="3.5.2" targetFramework="net48" />
|
2022-01-21 15:47:00 +08:00
|
|
|
<package id="Iesi.Collections" version="4.0.4" targetFramework="net48" />
|
2021-02-19 17:31:26 +08:00
|
|
|
<package id="Microsoft.AspNet.Mvc" version="5.2.7" targetFramework="net48" />
|
|
|
|
|
<package id="Microsoft.AspNet.Razor" version="3.2.7" targetFramework="net48" />
|
|
|
|
|
<package id="Microsoft.AspNet.WebPages" version="3.2.7" targetFramework="net48" />
|
8776: Upgrade Microsoft.CodeDom.Providers.DotNetCompilerPlatform to latest version (#8777)
* 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
2024-04-04 22:35:29 +08:00
|
|
|
<package id="Microsoft.CodeDom.Providers.DotNetCompilerPlatform" version="4.1.0" targetFramework="net48" />
|
2021-02-19 17:31:26 +08:00
|
|
|
<package id="Microsoft.Web.Infrastructure" version="1.0.0.0" targetFramework="net48" />
|
2024-12-06 16:49:25 +08:00
|
|
|
<package id="NHibernate" version="5.5.2" targetFramework="net48" />
|
2022-01-21 15:47:00 +08:00
|
|
|
<package id="Remotion.Linq" version="2.2.0" targetFramework="net48" />
|
|
|
|
|
<package id="Remotion.Linq.EagerFetching" version="2.2.0" targetFramework="net48" />
|
2024-12-06 16:49:25 +08:00
|
|
|
</packages>
|