Timeline for What's the most effective way to share code between .NET applications?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 2, 2013 at 15:37 | comment | added | Robert Harvey | Well, I agree with Eric King. Foundation code should be pushed as a stable version, not an unstable one. The key is maintaining a stable API: if you know the signatures of your foundation methods are not going to change, you can safely push the methods to Foundation and refactor them later without breaking anything. | |
| Oct 2, 2013 at 14:20 | comment | added | Josh | Maybe I wasn't as clear as I could be in my question. This is about what comes next. You've done all that, and now you need to share your code effectively between your different projects. Someone says "just use nuget for that" and it sounds great until you get into the details and run into problems - like how to synchronize different changes from different branches and applications. | |
| Oct 2, 2013 at 4:11 | history | edited | Robert Harvey | CC BY-SA 3.0 |
deleted 48 characters in body
|
| Oct 2, 2013 at 4:02 | history | answered | Robert Harvey | CC BY-SA 3.0 |