MSDN > フォーラム ホーム > AppFabric Service and Workflow Management > Does Dublin will require xalmx activation
質問する質問する
 

回答済みDoes Dublin will require xalmx activation

  • 2008年11月27日 16:13dominpo ユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダル
     
    Hello,
    I want to know if dublin will only permit to activate xamlx services and xamlx workflow services ?
    I mean that does using xaml is a requirement to host WCF & Workflow Services in Dublin ?
    Thx
    Regards
    Dominique

回答

すべての返信

  • 2008年11月30日 12:51Alan Smith MVPMVPユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダル
     
    Hi,

    I have hosted regular C# wcf services in Dublin, with an scv file as the URL. It seems to work fine, and I get the service level tracking working OK with it.

    Alan


    BloggersGuides.net
  • 2008年11月30日 19:18Chris CraftMSFTユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダル
     回答済み
    Dublin supports both declarative (XAML based) services and code based services. For activation you will need a XAMLX file or an SVC file.
  • 2009年2月23日 4:03Roman KissMVPユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダル
     
     Hi Chris,

    I am trying to manage the WorkflowServices v3.5 by Dublin (of course with some limitations based on the .Net3.5) and I having the following behavior in the MMC:

    1. the service makes two entries such as .svc and xoml
    2. the service name is empty for xoml workflow with a custom root activity 


    I think, the above is an implementation bug, isn't?

    Roman 
    Roman Kiss, MVP Connected System Developer
  • 2009年10月2日 17:35Chris CraftMSFTユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダルユーザーのメダル
     
    Roman, sorry for the long delay in following up on this.

    In the PDC build of Dublin we didn't have .NET version restrictions. We displayed and allowed you to configure any service we found. Since then we have added restrictions; Dublin will enumerate services built on earlier versions of the framework, but you'll need .NET 4 services to have the full Dublin experience.

    Thanks for the report about the empty service name for your xoml service. I'll have someone from the team look at this case.

    --chris