Service Fabric Mesh 中的 Actor 不工作 - 无法加载 DLL FabricRuntime.dll
Actor in Service Fabric Mesh not working - Unable to load DLL FabricRuntime.dll
我正在查看 Service Fabric 网格。到目前为止构建了一个 ASP.NETCORE API 应用程序 - 运行良好。
现在，我正在尝试按照 this tutorial 中的描述在新项目中添加一个（预定的）Actor。一切都很好，但在启动时我得到以下异常：
private static void Main()
{
try
{
ActorRuntime.RegisterActorAsync<SchedulingActor>((context, actorType) => new SchedulingActorService<ISchedulingActor>(context, actorType)).Wait();
}
catch
{
throw;
}
}
System.TypeInitializationException: 'The type initializer for 'Microsoft.ServiceFabric.Actors.Runtime.ActorRuntime' threw an exception.'
InnerException: DllNotFoundException: Unable to load DLL 'FabricRuntime.dll' or one of its dependencies: The specified module could not be found.
从最近的 announcement SF MESH 中，他们说 MESH 还不支持 actor 框架，并且会在未来的版本中支持，因为它需要访问 MESH 中不可用的底层平台资源。
SF Mesh is a multi-tenant service and so does not allow any access to the underlying VMs and all the deployments into SF Mesh are in containers. Services using actors, have dependencies that need access to the Nodes, and so currently there is no easy way to deploy them to SF Mesh, however providing a way for the customers to migrate their services from the SF clusters to SF mesh is in the roadmap and is planned to land prior to GA.
PS: 这个在页面底部的Q&A里说了
我正在查看 Service Fabric 网格。到目前为止构建了一个 ASP.NETCORE API 应用程序 - 运行良好。
现在，我正在尝试按照 this tutorial 中的描述在新项目中添加一个（预定的）Actor。一切都很好，但在启动时我得到以下异常：
private static void Main()
{
try
{
ActorRuntime.RegisterActorAsync<SchedulingActor>((context, actorType) => new SchedulingActorService<ISchedulingActor>(context, actorType)).Wait();
}
catch
{
throw;
}
}
System.TypeInitializationException: 'The type initializer for 'Microsoft.ServiceFabric.Actors.Runtime.ActorRuntime' threw an exception.'
InnerException: DllNotFoundException: Unable to load DLL 'FabricRuntime.dll' or one of its dependencies: The specified module could not be found.
从最近的 announcement SF MESH 中，他们说 MESH 还不支持 actor 框架，并且会在未来的版本中支持，因为它需要访问 MESH 中不可用的底层平台资源。
SF Mesh is a multi-tenant service and so does not allow any access to the underlying VMs and all the deployments into SF Mesh are in containers. Services using actors, have dependencies that need access to the Nodes, and so currently there is no easy way to deploy them to SF Mesh, however providing a way for the customers to migrate their services from the SF clusters to SF mesh is in the roadmap and is planned to land prior to GA.
PS: 这个在页面底部的Q&A里说了