VL dll export

once all Inputs and Outputs contained in a vl document are either marked as ungeneric, or can be completely inferred, is there anything else that would hinder an export of a proper .net dll?

1 Like

Well sadly yes, new issues came up when libraries reference .net standard. And as things are also developing very fast at .net core, we’re investigating a different route for export (and hopefully also runtime) which goes through roslyn. Up to now having high hopes for it, first tests look promising and if all works out we should end up at a much nicer spot than we were before. In any case dll/exe export is considered very important and is being worked on.


This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.