dotnet-svcutil adds package references with floating version
- Dominant language
- C#
- Stars
- 1.8k
- Forks
- 576
- Avg merge
- 6d 9h
- Merged PRs (30d)
- 2
Description
**Describe the bug**
Wenn adding a service to a project that doesn't have a dependency on the System.ServiceModel packages, these are automatically added with a floating version number (4.10.*). Please use a fixed version instead (4.10.0). Floating versions break build reproducibility and even patch versions can break stuff which leads to hard to diagnose problems.
I realize that NuGet package lock files would kind of fix this, but I don't want to deal with those because of a single dependency using floating versions. And most people wouldn't even realize the problem in the first place.
```
```
**To Reproduce**
Add a service to a project that does not have references to the System.ServiceModel packages.
**Expected behavior**
Use a fixed version (4.10.0 instead of 4.10.*)
```
```
Contributor guide
Assessment
This issue has not been assessed yet.