Timeline for Advice on Developing Shared Public Libraries in Visual Studio
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 29, 2023 at 1:54 | comment | added | Flater | @DocBrown: I know people are sometimes negative about shotgun debugging but I don't see it as an inherent negative. Shotgun debugging may not be the best default way of working but when you see no other way forward it is the more surefire way to progress to your goal (if slowly). | |
| Aug 28, 2023 at 20:56 | comment | added | Mark Olbert | Thanx, I think you've hit the nail on the head: I was mixing up two more-or-less incompatible things. | |
| Aug 28, 2023 at 20:54 | vote | accept | Mark Olbert | ||
| Aug 28, 2023 at 13:44 | comment | added | Doc Brown | This is an excellent answer. Just one comment here: IMO the wording "shotgun development" may sound a little bit too negative. Developing and refactoring libraries together with a consuming application is an excellent way for testing and validating the library functions and their usuabilty. Let me add I can confirm that releasing libs at defined point in time from a "main application" to other clients is definitely a useful strategy. Where I work, we are doing this for years, even before Nuget or the term "monorepo" were invented - this also works with different tooling. | |
| Aug 28, 2023 at 1:48 | history | answered | Flater | CC BY-SA 4.0 |