Skip to content
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.

Behavior and expectation mistmatch between KPM and K #195

Closed
muratg opened this issue May 16, 2014 · 3 comments
Closed

Behavior and expectation mistmatch between KPM and K #195

muratg opened this issue May 16, 2014 · 3 comments
Assignees
Milestone

Comments

@muratg
Copy link
Contributor

muratg commented May 16, 2014

KPM installs a newer version of a package, if the exact version of the package is not found.

Project.json

    [...]
  "dependencies": {
    "Microsoft.AspNet.Diagnostics": "0.1-alpha-build-0623",
    [...]

kpm restore

[...]
Resolving complete, 14738ms elapsed
Installing Microsoft.AspNet.Diagnostics 0.1-alpha-build-0624
[...]

k run however does not like that and complains.

[...] 
System.InvalidOperationException: Unable to resolve depedendencies
Microsoft.AspNet.Diagnostics 0.1-alpha-build-0623
[...]

Ideally KPM behavior should match K behavior.

@davidfowl
Copy link
Member

That seems pretty broken.

@davidfowl
Copy link
Member

@loudej why does kpm bump the version foward even if it's not a snapshot?

@davidfowl
Copy link
Member

Ok @muratg so the logic for the runtime will match kpm.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants