The document discusses the problems with DLL and package dependency management over time, from Windows 3.1 through .NET Framework 1.0 to NuGet. It proposes several solutions to avoid dependency and assembly binding issues, including service-oriented architecture with small, self-contained services; onion architecture with dependencies pointing inward; embedding dependencies using ILMerge/ILRepack; and source packages. It provides an example of how these solutions could be applied to a sales/warehouse system.

1. Escaping DLL Hell

2. João Bragança
//github.com/thefringeninja
//the.fringe.ninja/blog
@thefringeninja

3. eVision Software
Safety Software for Oil & Gas
Den Haag, Netherlands
//evision-software.com

4. Computing circa 1992
●Premium PC
o486 DX2
o16 MB Ram
o$3-$5k

5. Computing circa 1992
●Premium PC
o486 DX2
o16 MB Ram
o$3-$5k
●Windows 3.1

6. Computing circa 1992
●Premium PC
o486 DX2
o16 MB Ram
o$3-$5k
●Windows 3.1
●Extremely Limited by Today’s Standards

7. Computing circa 1992
●Premium PC
o486 DX2
o16 MB Ram
o$3-$5k
●Windows 3.1
●Extremely Limited by Today’s Standards
●Shared Memory

9. 2001 - .NET Framework 1.0
●AppDomain

10. 2001 - .NET Framework 1.0
●AppDomain
●Global Assembly Cache

11. Problems
●Pain of Manually Loading Assemblies

12. Problems
●Pain of Manually Loading Assemblies
●Must use Child AppDomain + Marshalling

13. Problems
●Pain of Manually Loading Assemblies
●Must use Child AppDomain + Marshalling
●Strong Naming

14. Escaping DLL GAC Hell

15. 2010 - .Net Package Managers
●OpenWrap

16. 2010 - .Net Package Managers
●OpenWrap
●NuPack

17. 2010 - .Net Package Managers
●OpenWrap
●NuPack
●NuGet

18. Problems
●Assembly Binding Redirect - Never Works
Right

20. Problems
●Assembly Binding Redirect - Never Works
Right
●Requires SemVer be Followed - It Isn’t

21. Problems
●Assembly Binding Redirect - Never Works
Right
●Requires SemVer be Followed - It Isn’t
●Strong Naming (again)

22. Escaping DLL GAC
Nuget Hell

23. Escaping DLL GAC
Nuget Hell
SHARED DEPENDENCIES

24. Solution

25. (Some) Upfront Design
Solution

26. Service Oriented Architecture

27. Service Oriented Architecture
●CORBA

28. Service Oriented Architecture
●CORBA
●DCOM

29. Service Oriented Architecture
●CORBA
●DCOM
●Web Services (WCF)

30. Service Oriented Architecture
●CORBA
●DCOM
●Web Services (WCF)
●Micro Services

31. Service Oriented Architecture
●CORBA
●DCOM
●Web Services (WCF)
●Micro Services
●Nano Services

32. Service Oriented Architecture
●CORBA
●DCOM
●Web Services (WCF)
●Micro Services
●Nano Services
●Femto Services

33. Service Oriented Architecture
●CORBA
●DCOM
●Web Services (WCF)
●Micro Services
●Nano Services
●Femto Services

34. Service Oriented Architecture
●CORBA
●DCOM
●Web Services (WCF)
●Micro Services
●Nano Services
●Femto Services

35. Service Oriented Architecture
Just Services.

36. Service Oriented Architecture
●[A Service is] a logical representation of a
repeatable business activity that has a
specified outcome

37. Service Oriented Architecture
●[A Service is] a logical representation of a
repeatable business activity that has a
specified outcome
●Is self-contained

38. Service Oriented Architecture
●[A Service is] a logical representation of a
repeatable business activity that has a
specified outcome
●Is self-contained
●May be composed of other services

39. Service Oriented Architecture
●[A Service is] a logical representation of a
repeatable business activity that has a
specified outcome
●Is self-contained
●May be composed of other services
●Is a “black box” to consumers of the service

40. Service Oriented Architecture
●[A Service is] a logical representation of a
repeatable business activity that has a
specified outcome
●Is self-contained
●May be composed of other services
●Is a “black box” to consumers of the service
●These are just fancy words for “a function.”

41. Service Oriented Architecture
public delegate Task<decimal>
GetAccountBalance(string accountNumber)

42. Service Oriented Architecture
●Use these functions for inter-component
communication

43. Service Oriented Architecture
●Use these functions for inter-component
communication
●Keep boundaries crisp

44. Onion Architecture
Solution

45. Onion Architecture

46. Onion Architecture
●Center Takes No Dependencies

47. Onion Architecture
●Center Takes No Dependencies
●Ports and Adapters

48. Onion Architecture
●Center Takes No Dependencies
●Ports and Adapters
●Dependencies Point Inwards

49. Onion Architecture
●Center Takes No Dependencies
●Ports and Adapters
●Dependencies Point Inwards
●Keep Implementations on the Outside
oDatabase
oHttp

50. OWIN
Solution

51. OWIN
●The only dependency is on mscorlib.

52. OWIN
AppFunc:
Func<IDictionary<string, object>, Task>
MidFunc:
Func<AppFunc, AppFunc>

53. OWIN
●The only dependency is on mscorlib
●Reduces Δ between production and
development

54. OWIN
●The only dependency is on mscorlib.
●Reduces Δ between production and
development
●Fast integration tests - possible to test entire
pipeline in memory

55. ILMerge / ILRepack
Solution

56. ILMerge / ILRepack
●Merges multiple assemblies into one

57. ILMerge / ILRepack
●Merges multiple assemblies into one
●Internalization

58. ILMerge / ILRepack
●Merges multiple assemblies into one
●Internalization
●Virtually eliminates shared dependency
problem

59. Source Packages
Solution

60. Source Packages
●SimpleJson

61. Source Packages
●SimpleJson
●LibLog

63. Source Packages
●SimpleJson
●LibLog
●netfx-Guard

64. Putting it Together
Solution

65. Putting it Together
Sales

66. Putting it Together
Sales Ware-
house

67. Putting it Together
Sales Ware-
house
GetInventoryCount
Func<string, Task<int>>
IsItemAvailable
Func<string, int, Task<bool>>

68. Putting it Together
Sales Ware-
house
GetInventoryCount
Func<string, string,
Task<int>>
IsItemAvailable
Func<string, int, Task<bool>>

69. Questions?

70. Resources
●//github.com/gluck/il-repack
●//owin.org
●//github.com/damianh/LimitsMiddleware
●//github.com/damianh/LibLog

71. João Bragança
//github.com/thefringeninja
//the.fringe.ninja/blog
@thefringeninja