Timeline for What's the most effective way to share code between .NET applications?
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 2, 2013 at 14:27 | comment | added | Josh | I"m not talking about managing glue code. We've already got a solution for that and it works well. I'm talking about sharing business logic. For example, our applications deal with managing organizations and people. So, we need to create a person, and there's a bunch of business rules associated with how a person should be created. Instead of creating it several times, we want to have one package that handles everything from constructing the object to persisting it that we share between the different projects that need to create people. | |
| Oct 2, 2013 at 9:24 | history | answered | Giedrius | CC BY-SA 3.0 |