Hi,

Thanks for the feedback. I can't tell you which one we will surely implement, but I can tell you which one we will surely NOT implement. :)

CSS Media Override:
This one will NOT be implemented. The design goal of our product is to render the output as closer to what user sees on SCREEN as possible, not for printing media. This is because most web developers do not create separate styles for print media or do not test printing media CSS as thorough. As such we will always follow screen output, not print output. If you must use print media, you can dynamically switch CSS with code;

MVC Helper:
This may be implemented in the future. However it will NOT be implemented on HtmlToPdf.ConvertUrl level. In another word, HtmlToPdf.ConvertUrl will not take MVC Action. It will be another object such ASPXToPDF that we current have;

Generate EMF Output:
No. This one will not be implemented. This is because we render as much as possible in vector format and we use float coordination (similar to GDI+). For example, we render SVG graphics, or CSS round corners in vector format so you can zoom in infinitely without losing quality. However those can not be expressed in EMF, which was very much based on GDI, not GDI+. As such this will not be implemented;

Generated XPS Output:
This can be considered.

Hope this helps.

Thanks!