Interpreter–part 6 of n–Ecosystem/usage

Series:

1. http://msprogrammer.serviciipeweb.ro/2018/07/16/interpreterpart-1-of-n/ – Idea
2. http://msprogrammer.serviciipeweb.ro/2018/07/23/interpreterpart-2-of-n/ – Coding
3. http://msprogrammer.serviciipeweb.ro/2018/07/30/interpreterpart-3-of-n/ – Testing
4. http://msprogrammer.serviciipeweb.ro/2018/08/06/interpreterpart-4-of-n/  – Deploy
5. http://msprogrammer.serviciipeweb.ro/2018/08/13/interpreterpart-5-of-n/ – Documentation
6. http://msprogrammer.serviciipeweb.ro/2018/08/20/interpreterpart-6-of-n/ – Ecosystem / usage

 

 

This is the latest – how do you use the component. In this case, the Interpreter is part of 2 separate projects : Stankins and AOP with Roslyn . Both uses this in order to interpret json files at runtimes.

For example, AOP with Roslyn wants to run in the current folder – not in the dotnet  folder wher it belongs.

So , for this, it has

“FolderName”: “@static:Environment.CurrentDirectory@”,

in the processme.,txt file.

The processme.txt is taken from

var pathDll = Assembly.GetEntryAssembly().Location;
path = Path.GetDirectoryName(pathDll);

But it processes files on the current directory – and it has the full name of the folder.