This project is read-only.

Occasionally, perhaps for the purpose of running some of the ActorFx samples, you might want to pull the ActorFx code down to your own machine, compile it and run it.  However, there is a potential hazard in doing this: it might be the case that the code that you’ve built (the latest/greatest ActorFx bits) might not be compatible with the ActorFx runtime bits installed on your machine.

One way to combat this problem is to be careful to pull down only the ActorFx code that matches the Actor runtime that you have installed. For example, if you’ve installed the runtime associated with ActorFx release 0.5, then you would want to sync to the code tree as of changeset 85133 (June 4).  You could then freely compile and run that code without any fear of the resulting application being out of sync with the installed actor runtime bits.

However, it may be the case that you want to sync to ActorFx bits that have been updated relative to the installed ActorFx runtime on your machine.  Perhaps you want to take advantage of a recently checked-in feature or bug fix, or perhaps you’ve made changes to the code yourself.  In this case, you will want to update the installed ActorFx runtime bits on your machine.  Here are instructions as to how to do that:

  1. From the ActorRuntimeManager, make sure that (in this order) all services have been stopped, all applications have been un-deployed, the runtime cluster has been un-deployed, and that the “Scour” operation has been performed.
  2. You then need to replace the actor logic in your installation area with the actor logic in your build area.  Do that by replacing the contents of [ACTORFX_INSTALL_ROOT]\ActorManifest\ApplicationPackages with the contents of [ACTORFX_SOURCE_ROOT]\NET\release\ActorManifest\ApplicationPackages. 
    • [ACTORFX_INSTALL_ROOT] is typically “C:\Program Files (x86)\MSOpenTech\Actor Framework”. 
    • [ACTORFX_SOURCE_ROOT] might be something like “C:\ActorFx\main\src”.  It represents the top of the “source” portion of our tree.
    • As of this writing, the contents that need to be transferred are the directories ActorGatewayApp, DictionaryActorApp, EmptyActorApp, ListActorApp and StatelessActorApp.  Transferring these from the build area to the installation area effective updates the “brains” of the installed actor runtime.

Having done the above, it should now be the case that any actors launched from the ActorRuntimeManager are compatible with the ActorFx code that you have built.

Good luck!  Contact us if you run into any problems with these instructions.

Last edited Aug 30, 2013 at 4:08 PM by joehoag, version 4


No comments yet.