Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MonoDevelop project dependency version/tag problem #551

Open
ohenley opened this issue Oct 31, 2014 · 1 comment
Open

MonoDevelop project dependency version/tag problem #551

ohenley opened this issue Oct 31, 2014 · 1 comment

Comments

@ohenley
Copy link

ohenley commented Oct 31, 2014

Hi!

When I load my app solution that depends on vibe.d, MD keeps opening files from an old vibe.d tag even if I state otherwise in my dub.json file. (e.g: open files from vibe-d-0.7.20 instead of specified vibe-d-0.7.21-rc.2 in my dub "solution" config file.)

Deleted vibe-d-0.7.20 from ~.dub/packages. Then MD when reopened will load files from another vibe-d tag, this time vibe-d-0.7.21-rc.3, also installed on my computer, but still not the one specified in my dub "solution" config file.

* workaround*: delete every version/tag except the one you need. MD has no other choice than to load the good one. :)

my setup: MonoDevelop 5.7, D language binding 2.5.2, DUB 0.9.22, Debian 7.1 64 bit.

thx,

olivier

@aBothe
Copy link
Owner

aBothe commented Nov 1, 2014

Okay, that's probably even a 'feature request' then, not a bug - the version selection isn't implemented completely yet.

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

No branches or pull requests

2 participants