Built a PDF generator in .NET c#

The PDF library would need to be called from BB which is a C# .Net MVC project (I believe it is currently using MVC5 libraries). The PDF library would need to be a .NET class library ideally written in C# for future development. Other development technologies could technically be used as long as they can operate on a windows server and have a .net class library wrapping the main input/outputs of the code. This is for our software product called BB, and I'll briefly explain. BB does a lot of things, but one of the core processes is to take HTML that is rendered on the screen in a browser (Chrome) and generate a hi-res PDF that can be commercially printed. Imagine a flyer or printed advertisement as the output. We are currently using a module (now built into BB) that we purchased from a company I think in Europe, after experimenting with a number of different modules. The current module we use is OK, but it's not as good as we want it to be. And because it's basically a black box to us, we can't fix the flaws we are now seeing in it. For a sense of this, here are some of our challenges: • Font wrapping - fonts on the screen are rendering slightly different than fonts in the PDF. We have worked around this by studying different fonts and only use those in BB where the differences are slight...but it still creates issues. • Processing errors - the black box is triggering out-of-memory issues on the web server during some of our batch processing routines and we don't really know why. • Resolution control - we want to be able to provide an input variable and tell the black box the resolution of the output in the PDF-- i.e. 300 DPI or 150 DPI. • Color Management - We would like to be able to tell the back box to output the PDF in CMYK or RGB color formats. • etc. We'd like to be able to provide specs (inputs and outputs) and have the developer build us our own PDF generator that we'd have more control of. The complexity is such that the developer would need to have very strong experience with: • How PDF files are built and work...inside the guts of the file. • Color management -- most developers know nothing about color management, other than on a computer monitor. Generating a PDF for a printer requires color profiles and all sorts of color management, that is ultimately built into the PDF file, that is "ripped" by the printing company's pre-press software as it makes the printing plates. • Font management. Adobe does this seamlessly. Most developers know nothing about how screen fonts and printer fonts work. For us to eliminate font wrap differences between the screen view the PDF, someone needs to understand fonts.