This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
When upgrading from LightSpeed4 to LightSpeed5, the ability to use relative paths for Design Time Assemblies is lost. This was fixed in a nightly build of LightSpeed4. Thanks, Jason Moore |
|
|
|
|
Hi Jason, 5.0 contains all of the nightly updates from 4.0 so this sounds like it may be a regression of some kind - which nightly build were you previously using where this was working? Ill have a look into getting a fix applied as soon as possible.
|
|
|
|
|
It has worked in every version of 4 since the issue was resolved, we are currently using LightSpeed40Professional-20130109. We just decided to look at migrating to version 5 today. Thanks for the quick response, Jason Moore |
|
|
|
|
Thanks - Ill look into this and get back to you with an update once I can determine whats going on :)
|
|
|
|
|
Hi Jason, Ive had a look at this and the resolution of relative paths is certainly still in there. Are you seeing an error when you attempt to save indicating that the Design Time Assembly could not be loaded? If so what is the error you are seeing? I am wondering if this might be a case in which the working directory is not the one which the model lives in as the starting point when we go to resolve the file path for the assembly.
|
|
|
|
|
I apologize for wasting your resources on this, the design time assembly name got reverted somehow and I didn't catch it until I just tried to supply screenshots. Thanks for your help, I'll try to research the issue more thoroughly next time. Great Product! |
|
|
|
|
Thanks Jason - glad to hear its all sorted :)
|
|
|
|
