Reputation: 89661
Say I have low-level utility assemblies with some basic classes.
Then I have other higher-level assemblies which use those classes, potentially taking them as parameters and returning them.
Now, at the application level in the solution, if you add a higher-level assembly which uses lower-level assemblies in this manner, if you don't add references to the lower-level assemblies, the application will not compile.
Is there a way to indicate that a reference to an assembly requires other references to be exist or be added?
Upvotes: 4
Views: 150
Reputation: 9389
You can create a NuGet package, and use the command line to add a reference to your assembly
Upvotes: 1