Skip to content
This repository has been archived by the owner on May 9, 2024. It is now read-only.

Entry point for Azure Service Fabric #27

Open
alexey-belous opened this issue Dec 10, 2018 · 1 comment
Open

Entry point for Azure Service Fabric #27

alexey-belous opened this issue Dec 10, 2018 · 1 comment

Comments

@alexey-belous
Copy link

Hi,

I faced up with following issue, that may be related to this one: microsoft/service-fabric-aspnetcore#22 . The problem is that entry point, represented as dotnet service.dll (see the lines below) works only in Service Fabric hosted in the Docker container, but doesn't work in Azure Service Fabric cluster.

https://github.com/Microsoft/generator-azuresfcsharp/blob/dcb2d56752e7b01dfa82b2b2fd83842f58506d55/generators/CoreCLRStatelessService/templates/service/app/appPackage/servicePackage/ServiceManifest.xml#L15-L20

And to make it work on Azure Service Fabric I should change manifest as follow:

<EntryPoint>
      <ExeHost>
        <Program>Service.exe</Program>
        <WorkingFolder>CodePackage</WorkingFolder>
      </ExeHost>
    </EntryPoint>

So my question is if there's a posibility to have universal ServiceManifest for both environments?

@mikkelhegn
Copy link

It's about the .net core deployment type (framework dependent vs. self-contained). Take a look at this issue: https://github.com/Azure/service-fabric-issues/issues/500

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants