I suggest you ...

One assembly for referencing

Now to reference Unity I need to reference 3 asms: Unity/Unity.Configuration/System.Configuration. Change it to only 1, please. When I'm allways trying that my component user feel comfortable to reference only one "business logic" assembler, I should instruct them also to reference three additional dlls...

41 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    AnonymousAnonymous shared this idea  ·   ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • KarlKarl commented  · 

        I'm against this suggestion too. Agree with Dzmitry

      • Dzmitry LahodaDzmitry Lahoda commented  · 

        I am against this idea.
        1. Client apps can use unity but not configuration. Configuration slows down start up time and increases download size - both are important not to be there of client apps.

        2. You have option to merge on il basis (try ILMerge or https://github.com/gluck/il-repack) or projects build basis (try SharpDevelop NRefactory and MSBuild dlls)

      Feedback and Knowledge Base