How to specify a minimum version requirement of a dependency in a nuspec file?
I have two libraries that I use in several projects. They are MCData.vA.B.C.dll and MCConfig.vA.B.C.dll. The vA.B.C values reflect the assembly version of the released build. The nuspec unique package identifier is <id>MCConfig</id> or <id>MCData</> respectively (ie without the version data). I use a private repository to store them.
How to specify a minimum version requirement of a dependency in a nuspec file?
I have two libraries that I use in several projects. They are MCData.vA.B.C.dll and MCConfig.vA.B.C.dll. The vA.B.C values reflect the assembly version of the released build. The nuspec unique package identifier is <id>MCConfig</id> or <id>MCData</> respectively (ie without the version data). I use a private repository to store them.
How to specify a minimum version requirement of a depenency in a nuspec file?
I have two libraries that I use in several projects. They are MCData.vA.B.C.dll and MCConfig.vA.B.C.dll. The vA.B.C values reflect the assembly version of the released build. The nupsec unique package identifier is <id>MCConfig</id> or <id>MCData</> respectively (ie without the version data). I use a private repository to store them.
How to specify a minimum version requirement of a depenency in a nuspec file?
I have two libraries that I use in several projects. They are MCData.vA.B.C.dll and MCConfig.vA.B.C.dll. The vA.B.C values reflect the assembly version of the released build. The nupsec unique package identifier is <id>MCConfig</id> or <id>MCData</> respectively (ie without the version data). I use a private repository to store them.