lkosson
commented
3 years ago It's mostly about lack of testing and no official support from Microsoft.
There are four major differences between this package and official one:
- expression compiler changed from VB do Roslyn
- report unloading using AssemblyLoaderContext instead of AppDomain
- removed report sandboxing / code security
- removed spatial types, maps and charts support
If you have fixed set of RDLCs that come from trusted source, if they load and render correctly using this package, most likely you are good to go.
I'm generating PDFs using RDLC from a asp.net web api, and need to upgrade to asp.net core. This project looks very interesting but the readme states that it isn't ready for production use. In what ways isn't it ready, and do you have an estimate for when it might be?