NeVeS

I know, I know. After a new version of scriban has been released, I will translate all available examples from Typewriter documentation to NTypewriter syntax. Until then, maybe @gregveres will...

I have added a few examples to [documentation](https://github.com/NeVeSpl/NTypewriter#examples).

We will see about that, officially only .net standard 2.0 and C# 7.3 are supported in the custom function.

There are no [Built-in functions](https://github.com/NeVeSpl/NTypewriter/blob/master/Documentation/BuiltInFunctions.md) that operate on files, but you can always write your own [Custom function](https://github.com/NeVeSpl/NTypewriter/blob/master/Documentation/CustomFunctions.md#Custom-functions) that will do it.

Do not worry about that, it is about deploying Blazor version to the server, which should not be done for PRs anyway. I will review this PR in the next...

That behaviour was introduced here #75. In general, it is a good idea to split `Save` into two functions: `Save` and `AddSource`, but as you already noticed #106 adding *.cs...

I would prefer to add a flag `AddToCompilation` on `NTypewriter.RenderedItem` instead of using `IGeneratedFile ` as a marking interface, anyway `NTypewriter` does not have a reference on `NTypewriter.Runtime`, so using...

What would you say about placing that information in a tooltip?  That already is implemented, but there is a bug here: https://github.com/NeVeSpl/RevitDBExplorer/blob/86acb0ba5d84e8b71b910f5d8bebc0853672cc87/sources/WPF/Converters/FeetToMetersConverter.cs#L16 should be `typeof(double).GetCSharpName()` instead `"Double"` PR welcome...

sure, you can do every not time-consuming change you want without asking, we will be thinking about its fate during PR review.

Indeed, there is a lot of caching going on behind the scene, and NT was written when integration VS with git was not a thing yet. I will look into...