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
First I just want to say thank you for creating this project. It has been a big help!
I have a couple of non-framework assemblies that my scripts use. Would it be better to create reference assemblies for them and use those during compilation, instead of the actual implementation assemblies?
Thanks,
-Jake
The text was updated successfully, but these errors were encountered:
First I just want to say thank you for creating this project. It has been a big help!
Thanks. Glad you're getting use out of it :)
I have a couple of non-framework assemblies that my scripts use. Would it be better to create reference assemblies for them and use those during compilation, instead of the actual implementation assemblies
For .NET Core I would always recommend using reference assemblies when possible. Those will have consistent API surface area from release to release. Where as implementation assemblies are free to change surface API area by moving around types.
Hello Jared,
First I just want to say thank you for creating this project. It has been a big help!
I have a couple of non-framework assemblies that my scripts use. Would it be better to create reference assemblies for them and use those during compilation, instead of the actual implementation assemblies?
Thanks,
-Jake
The text was updated successfully, but these errors were encountered: