Fix the way we handle versions in packages.config and for nuspecs to align with NuGet.exe · Issue #780 · scriptcs/scriptcs · GitHub
Skip to content

Fix the way we handle versions in packages.config and for nuspecs to align with NuGet.exe #780

Description

@glennblock

If a range is specified for version:

<package id="ScriptCs.Contracts" version="[0.3.1,1.0]" targetFramework="net45" />

installing will fail with the folllowing error:

ERROR: Installation failed: Unable to parse version value '[0.3.1,1.0]' from 'packages.config'..

ranges are supported per nuget docs: http://docs.nuget.org/docs/reference/versioning

Also when installing a package, we should honor the same rules as nuget for package dependencies in the metadata such that a version is either a minimum version or a range. Currently we do an exact match.

For both packages.config and nuspecs we should support the proper semantics.

Metadata

Metadata

Assignees

Labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions