Yes, this one has been reported to us a couple times; it's fixed in our internal bits and the fix will be in the next release.

By on 12/7/2009 10:32 AM ()

Any way to get those fixed bits? Any estimate on next release? This really makes team dev a major pain!

By on 12/7/2009 5:59 PM ()

The next CTP release will probably be along with the VS2010 final release.

In your original message, you say you have to edit 'each time you check out the project'. Can you clarify? Surely you can edit the .fsproj file to change the path to be relative and check in the .fsproj-with-correct-relative-info into source control? So you should have to do this at most once per reference, yes? Or am I missing something? It is a very annoying bug (especially to me, as it is my fault, argh), but my understanding is that for Beta2/CTP the impact is that you can effectively fix it 'once and for all' for a given reference via a manual edit... I just want to ensure I'm not missing anything, and that we have tested everything and don't have any other looming bugs here.

By on 12/8/2009 9:52 PM ()

Alternatively, you can use subst to "mount" your source tree as a drive, and then use absolute paths rooted in this virtual drive.

If you have a project you need to refer in C:\mydata\projecttree\project, and if every developer uses the same hierarchy in projectree, mount C:\mydata\projecttree as X:

subst X: C:\mydata\projecttree

Then set references to X:\project

By on 12/10/2009 11:24 AM ()

Brain

I haven't actually tried that (I say while slapping my forehead)! I'll give it a shot. At least that way we'll only have to deal with it on new references added -- which at this point is fairly seldom.

Thanks

Bill

By on 12/10/2009 5:41 AM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper