Needing to deploy a controller into Cloud Services rather than Websites, best approach

Question

My MVC3 / SQL Azure runs great on Windows Azure WebSites. However there is one feature, implemented by one controller which creates a PDF document. This, I have now found out, is not allowed on WebSites, since the component I use, and many similar access GDI natively. In essence, it requires full trust. This component works fine on Cloud Services, I guess as a Web Role. I am following advice from the supplier here. However I do not want to port my entire application across, so I have come up with the idea of creating one webRole for this specific controller. It accesses the same SQL Azure instance as the WebSites install.

So my question is what would be the simplest approach to implement this as a standalone service on WACS which would then be called via the main Web Application on WAWS? Also one should not be able to access this WACS directly from a URL. It is like a child controller of that in the WAWS hosted application.

Thanoughts

Answer 1

There are two options:

1-)create a WCF and host it in Cloud Services (Web Role).

2-)create another aspnet mvc web application and copy just this controller and publish it to cloud services.