Releases: aspnet/RoslynCodeDomProvider
v4.1.0 WebSites release
Introduces a new support package to enable proper integration of the 4.X series of the Microsoft.CodeDom.Providers.DotNetCompilerPlatform
package with project-less "Web Sites." This package does not contain any libraries or providers of it's own. It simply restores the old 'install.ps1' nuget functionality to its tightly coupled 'DotNetCompilerPlatform' package dependency. Powershell installation was the only way to integrate with "Web Sites" which have very limited msbuild support.
v4.1.0 release
-
Refreshed current compilers:
In keeping with the new versioning scheme for this project, the version has been revved to 4.1 to match the version of the compilers included. -
No more old compilers:
Stop carrying old versions of compilers. If you upgrade to get new compilers, you get new compilers. The old compilers that might carry references to binaries that get flagged in security scans even though the binaries don't get copied to the ouput directory... they just won't be included in the package anymore. -
.Net >= 4.7.2 Required:
As a result of not keeping older compilers packaged in this project, we can no longer support versions before 4.7.2 because compiler versions 3.0 and newer only support 4.7.2+. -
Move to msbuild targets - away from install.ps1:
Nuget has moved on from install.ps1. We had one foot in the msbuild camp before, and one foot still in the install.ps1 camp. The 4.X releases jump fully into the msbuild ecosystem with both feet.
v3.11.0 release
Refresh compilers to 3.11... the most recent and likely last of the 3.X major releases.
-
Refreshed compilers:
In keeping with the new versioning scheme for this project, the version has been revved to 3.11 to match the version of the compilers included. -
Only support .Net >= 4.6.2:
Older versions of .Net are out of support, so this update also removes support for them and no longer carries the oldest version of the compiler tools that was used in previous versions. -
Non-web projects:
The appSettingaspnet:RoslynCompilerLocation
can still be used to point at a specific download of the Roslyn compiler tools, but this package is hopefully a little more forgiving when searching for a default location and should accomodate both web projects as well as non-web projects without requiring this setting.
v3.6.0 release
Several bug fixes. Some more prominent changes:
- Update to 3.6 .Net compilers... in particular enabling C# 7.3 for .Net projects using this package.
- Config de/hydration feature so changes to compiler config are not lost when upgrading this package.
- Ability to turn off auto-enabled compiler arguments that exist for ASP.Net scenarios.
- Shift to for configuring the CodeDom provider instead of global appSettings switches.
- Fix bugs in .Net Core MSBuild scenario.
v3.5-preview
V3.5-preview1 doc update. (#106)
2.0.1 release
- Fixed issue #52
- Updated the Roslyn version to 2.9.0
2.0.0-preview
- Remove the dependency of Microsoft.Net.Compilers from the nupkg
- Fix rebuild/clean warning issue (Details can be found in this PR)
- Update build script
v1.0.8 release
•Fix two publishing issues reported on this thread
•Update the reference version of Microsoft.Net.Compilers
v1.0.7 release
Address the publishing issues introduced in 1.0.6 release.
v1.0.6 release
- Fixing issue#2 & issue#10
- Adding support for custom location of Roslyn binaries