>>https://blogs.msdn.microsoft.com/bharry/2017/03/31/shutting-down-codeplex/
>>
>>Looks like those projects currently hosted there will need to find a new home.
>
>The VFPX team is aware and already discussing next steps.
>
>Tamar

when migration strategy is clear, might be a good idea to migrate Thor to gitHub first so that we can help the team adapting the 'update tools' feature to the new environment.

Extant tools like grunt, gulp, bower, chocolatey (pick any) are benchmarks we can learn from to implement these new update chores

One option is to use any of them out of the box -- most (probably all) require installing node.js in the dev env. -- a no brainer IMO: we use bower to update FoxInCloud JavaScript dependencies.

Another benefit: it'll give the VFP community a fresh jump start into the marvelous world of JSON

one constraint is to consistently use version tags meeting the semantic versionning specification

I can probably help in this area (maybe Rick Strahl too).