Star Wars : Rogue One, Type Provider edition

by Pezi 19. January 2017 07:18

A LONG TIME AGO, IN A GALAXY FAR AWAY…..

Having infiltrated the Empire’s data centre, you are not overly surprised to discover they are using some ancient system from the old republic days.  A brief look around reveals a monstrous legacy Empire Enterprise system.  It has a ORM you thought had died out millennia ago.  You can immediately see no less than 13 layers of inheritance, 6 levels of dependency injection, and some complete bastard has spread the evil EmpireAutoLogger all over the place

r11

Thankfully, being a Jedi fighting for the Rebellion, you have access to both the force and the latest database access technology, F# type providers.  Using this power, you are able to access the remote database controls, where a large crane/arm can be manoeuvred in order to pickup the legacy hard drive containing the Death Star plans.

There is one problem.  The lag here is terrible, the Empire are onto you, and the location of the disk in questionable.  In fact, it seems the longer you take to get the crane into position (IN REAL TIME!), the more likely the disk is to change position completely.

r12

Can you grab the disk before it is too late?

TO HELP THE REBELLION!

(NOTE. You MUST change your tooltip font to a monospace font. I suggest Lucida Console in at least 16pt.)

Grab the InteractiveProvider from my github here, build it, then create a script file and reference the type provider. Since the InteractiveProvider dynamically loads assemblies that contain types implementing the interfaces it is looking for, you will have to tell it as a static parameter the directory that the rogue one dll resides in.

r3

May the force be with you, always.

Tags:

Add comment

biuquote
  • Comment
  • Preview
Loading