Bug #6191
closed![Author: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=50&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
![Assignee: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=22&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
Released SaxonCS artefact is a debug build
0%
Description
Email from Nick Trevor:
Sorry to reach out directly, but was wondering if you could help. I'm test the performance of SaxonCS and when running the benchmarks I am getting warned that the nuget package is a debug build which could impact performance. Is it possible to get a release package published to nuget?
// * Assembly Benchmarks which defines benchmarks references non-optimized SaxonCS
If you own this dependency, please, build it in RELEASE.
If you don't, you can disable this policy by using 'config.WithOptions(ConfigOptions.DisableOptimizationsValidator)'
Updated by Norm Tovey-Walsh 11 months ago
It's always interesting trying to work out what options the Microsoft build tools really want you to use.
AFAICT, we are making release builds not debug builds (--configuration Release
) but we also specify a DebugType
of pdbonly
in the .csproj
file. I wonder if that's relevant?
It does appear that we are setting Optimize
in the .csproj
file to false
. Perhaps we should set that to true
.
Updated by Norm Tovey-Walsh 9 months ago
I've changed the defaut for Optimize
to true
.
Updated by Michael Kay 2 months ago
- Status changed from New to Closed
- Fix Committed on Branch 12, trunk added
- Fixed in Maintenance Release 12.4 added
I'm closing this in the hope that the changes we made to the build fixed the problem. If not, please let us know.
Please register to edit this issue