roadmap

[JonasSamuelsson]

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?

[lkosson]

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.

[tiza82]

@lkosson are there any plans to have this package available for .net standard 2.0? Not sure about the feasibility of this, but in most cases, when migrating several projects from .net framework to .NET, the first step is to move the libraries that are dependencies to .net standard so you can then start migrating to .NET all the projects using those dependencies. So migrating the dependency to .NET directly is not an option.

[lkosson]

There is not assembly unloading support in .NET Standard, so using such version of RVC server-side would massively leak memory for each report generated. Apart from that - it might be possible, but see #182 for further discussion.

[tiza82]

Thanks for the answer @lkosson !