Inner workings and documentation

Hello,

Thank you for this project! It proves that an idea of mine is feasible and inspires to pursue it.

Could you please explain how does it work internally? Especially the Power Query execution part. I’ve been trying to figure that out by following the code but lack of C# and .NET familiarity limits my research to guesswork.

From what I’ve gathered, the magic happens here: Commands.cs, namely in the instance of QueryExecutor class. Where does that class come from? Is there any documentation for it?

It seems that QueryExecutor is imported from one of the Microsoft.Mashup.* libraries in the beginning of the file, but I was unable to find any documentation about those.

Please expand/correct my findings and point me to the relevant documentation.

Thank you!

[otykier]

Just a heads up, in case you’re planning to use PowerQueryNet or a similar technique in a production scenario, where there is a risk of a Microsoft license/EULA audit on your company:

In addition to being not supported by Microsoft, interacting with the mashup engine in any other way than through the Power Query UI in Excel / PBI / SSDT is explicitly breaking the EULA 😦

[landall]

Now the fun about the licencing, for example in Czech Republic you are allowed by law to reverse engineer sw. So it ,mostly depends on local law.

reverse engineer is also allowed in some other countries for study purpose. use an undocumented API from the result of other’s study is also allowed. so…