You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on a software that injects itself into a program to extend its features with an unofficial plugin support.
I would like to be able to provide builds more easily using continuous integration, but since the software it uses as a reference is proprietary, I cannot legally bundle it. So it forces me to use reflection for the entire software which is not a convenient workflow at all.
Proposal
It would be nice to be able to export a stub project from a source exe or dll.
The stub project would contain the interface to the program without the actual implementations, which would make it easier to add to continuous integration workflows where we can't bundle the program, the dependencies would get resolved at runtime anyway.
Alternatives
It's currently possible to export a visual studio project and manually remove the implementation from all methods but this is clearly impractical for a big project.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Problem Description
I am working on a software that injects itself into a program to extend its features with an unofficial plugin support.
I would like to be able to provide builds more easily using continuous integration, but since the software it uses as a reference is proprietary, I cannot legally bundle it. So it forces me to use reflection for the entire software which is not a convenient workflow at all.
Proposal
It would be nice to be able to export a stub project from a source exe or dll.
The stub project would contain the interface to the program without the actual implementations, which would make it easier to add to continuous integration workflows where we can't bundle the program, the dependencies would get resolved at runtime anyway.
Alternatives
It's currently possible to export a visual studio project and manually remove the implementation from all methods but this is clearly impractical for a big project.
Additional Context
No response
The text was updated successfully, but these errors were encountered: