Skip to content

Instantly share code, notes, and snippets.

@jamesmacfie
Last active March 2, 2017 01:13
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jamesmacfie/2fd509291b31457f6986fbb30d38f800 to your computer and use it in GitHub Desktop.
Save jamesmacfie/2fd509291b31457f6986fbb30d38f800 to your computer and use it in GitHub Desktop.
How to publish a new version of the recorder

How to publish a new version of the recorder

Open the PointGrayRecorder solution in Chimera

It lives at https://github.com/8i/Chimera/blob/master/Recorder/V1/PointGrayRecorder/PointGrayRecorder.sln. Lol.

Alter the server app post build step

I've never got the post build steps to run. When I first got the recorder setup on my machine with Bob's help we simply deleted the code in here as it wasn't needed for the ServerApp project. So you should just do this too. Only thing to remember here is to not commit this change.

Make your changes!

Simpy make the changes you need and test them locally.

Publish the app

For this to be automagically updated the next time the user opens the Studio you'll need to make sure it is published to the same folder location as it was installed from. This is due to the MS ClickOne install wizard.

For LA this need to be set to

\la-nas1\Storage\Software\8iBuilds\ServerApp\Studio\

which means you'll need to be on the same network as the LA studio.

The latest version number should increment itself.

Commit your code

There are some chunks in the .cdproj code you'll probably want to ignore. The only real change you need to commit is the change to ApplicationRevision which dictates what the next version number will be.

Reopen the recorder on the master machine

On master you just need to reopen the recorder app. If all goes well you'll see a wee "Do you want to update" box come up when you restart. Do that and when you log in the version number listed up the top left will also have been incremented.

Dance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment