Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

14
  • 24
    +1, although I think there is an element of humor in someone working with .NET being concerned about dragging in irrelevant code via a DLL reference. Commented Apr 5, 2013 at 19:28
  • 2
    @ColeJohnson .NET in itself IS a huge reference! Probably much bigger than the dlls I'd make myself. Commented Apr 6, 2013 at 12:02
  • 2
    I get that. However, .NET's JIT compiler only loads the required methods into RAM (when they are called) Commented Apr 6, 2013 at 20:07
  • 1
    True. Although you still have to distribute the whole .NET framework to anyone who wants to use your product, and big projects and complex solutions are more difficult to manage. Commented Apr 8, 2013 at 10:39
  • 2
    Related: When is a 'core' library a bad idea? Commented Jun 25, 2013 at 7:45