Home/ Questions/Q 498845
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T05:55:30+00:00

I’ve been thinking about ways to refactor a fairly expansive class/utility library I have,

  • 0

I’ve been thinking about ways to refactor a fairly expansive class/utility library I have, and one thing I think I want to do is split off any higher-level helper utilities that introduce new dependencies. I read some previous questions here, and one that I particularly noticed was a comment about how Microsoft freely uses namespaces across DLLs. The example given was System.Web – it’s in the base framework, but there’s also a System.Web.dll that adds more functionality to the namespace if you want it.

I also noticed several other System.Web.* DLLs available, and I was wondering if there’s a reason why they wouldn’t be combined into a single DLL. Could it be that they have their own individual dependencies and Microsoft (like me) wanted to separate assemblies along those lines? Or is it for easier maintenance? Something else entirely?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The reason they are not 1 .dll is because different versions of the framework.

    System.Web under version 2.0

    System.Web.Abstractions,
    System.Web.DymanicData,
    System.Web.DymanicData.Design,
    etc. . . .
    System.Web.Extensions

    are all written under the 3.5 framework.

    If you changed System.Web to be 1 .dll and then all users would have to change the .NET 3.5 framework, IIS still uses 2.0.

    • 0