Saxon

Feature #2873

Updated by O'Neil Delpratt about 5 years ago

Hi, 


 


 We've found that the new .NET Core CLI (even when targeting a .NET full framework like 4.5.1) does not copy all necessary assemblies when creating a build. This results in a 'System.IO.FileNotFoundException' (Could not load file or assembly saxon9he). 


 


 The package has a configured filtered assembly reference to 'saxon9he-api.dll' (see attachment, bottom-left corner). 


 


 We've created a local package based on the Saxon-HE 9.7.0.7 package and testes the following two cases: 

 

 1. Add the 'saxon9he.dll' to the Filtered Assembly Reference 

 

 1. Remove both files from the Filtered Assembly Reference, so there is no filter applied at all 


 


 We came to the conclusion, that when having no filtered assembly references or having both of them explicitly set, both the 'saxon9he.dll' and 'saxon9he-api.dll' gets copied to the bin folder. When specifying only a single assembly reference, only that single assembly gets copied (that is the case for Saxon-HE 9.7.0.7 package when using the new .NET CLI). 


 


 The same sort of discussion was going on GitHub at: https://github.com/dotnet/cli/issues/3929 


 


 Our guess would be to also add the 'saxon9he.dll' to the Filtered Assembly Reference for the NuGet package. 


 


 Is it possible for Saxonica to fix this in the next package release?  
  

Back