New answers tagged

1 vote

Is updating to a new .NET-version a major or minor version change when using SemVer?

Unless there is a change to the functionality of the code. Don't change the version number. You can build your library to target multiple framework versions. The compiled dlls should all have the same ...
user avatar
  • 64.6k
6 votes
Accepted

Is updating to a new .NET-version a major or minor version change when using SemVer?

Unless the update to the .NET Framework would affect consumers of the package or its API, I would increment the patch version number when updating dependencies. Both the major and the minor version ...
user avatar
  • 76k
2 votes

Hardcoding endpoints in library alternative

Option 2 is fairly common in today's projects, but it's because of the frameworks. Many support configuration overloading out of the box. A pattern of configuration overloading by source could be *: ...
user avatar
  • 11.7k
1 vote

Hardcoding endpoints in library alternative

As @Doc Brown said, there is no one right answer, but when it comes to libraries, I tend to err on the side of flexibility and not making decisions for the consumers of my library. What happens if ...
user avatar
3 votes
Accepted

Hardcoding endpoints in library alternative

How much configurability a software requires, and how much hardcoding of such parameters is acceptable depends highly on the way how the software will be operationally used. For example, do you expect ...
user avatar
  • 185k

Top 50 recent answers are included