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.
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