I've seen a few posts discussing this scenario, but I'm still struggling with what might be the best solution...
1. I've a rehosted designer to allow users to create XAMLX
2. These XAMLX are stored on a database
3. I now need to be able to expose these XAMLX in IIS to be consumed by clients
4. Clients will be able to compose the right addresses to reach these XAMLX. Examples:
http://server/WFSite/V2/MyService.xamlx; or similar for non-http protocols
My question is, what is the best solution to load and expose the xamlx services in IIS?
Possible solutions that I've found so far:
1. Use a ServiceHostFactory with a ServiceHost to load the XAMLX from the database
a. Requires an .svc file for each .xaml file stored in database. The .svc file is needed to specify the ServiceHostFactory for each XAMLX.
b. Clients would reference the XAMLX by referencing the .svc endpoint address
View Complete Post