Gentlemen,
Thank you for your replies/discussion on the topic.
I am no stranger to C++/CLI or other managed to unmanaged interop, I had no doubt that this would have been the answer.
That is the 'what' but I'm more interested in the 'how' at the moment.
There is numerous tutorials and walkthroughs for creating Native MDL applications or .Net addins, there is no examples of a cross over between the two which is the reason why I questioned the feasibility of this. The thing that I can't get my head around is building a Native MDL dll without Bmake especially as that seems to be the recommended means of compiling a Native MDL dll.
All I want from the Native MDL is the output of the IElementGraphicsProcessor which I have all the code to do and have tested it in a standalone Native MDL application but can't find the minimum requirements of libs, headers etc in the documentation to do this in a standalone dll.
Going for .Net addin dipping into MDL rather than the other way around would be my preferred way of doing this because our own application is mainly .Net based so would make the linking easier.
Does anything exist for the above?
Thank you for your replies/discussion on the topic.
I am no stranger to C++/CLI or other managed to unmanaged interop, I had no doubt that this would have been the answer.
That is the 'what' but I'm more interested in the 'how' at the moment.
There is numerous tutorials and walkthroughs for creating Native MDL applications or .Net addins, there is no examples of a cross over between the two which is the reason why I questioned the feasibility of this. The thing that I can't get my head around is building a Native MDL dll without Bmake especially as that seems to be the recommended means of compiling a Native MDL dll.
All I want from the Native MDL is the output of the IElementGraphicsProcessor which I have all the code to do and have tested it in a standalone Native MDL application but can't find the minimum requirements of libs, headers etc in the documentation to do this in a standalone dll.
Going for .Net addin dipping into MDL rather than the other way around would be my preferred way of doing this because our own application is mainly .Net based so would make the linking easier.
Does anything exist for the above?