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
|
Hi, The current installer doesn't seem to support setting explicitly the installation directory. Is there a tangible reason for this? |
|
|
Hi, We removed this feature from the installer right back when we release LightSpeed 1.0. The reasoning being that nobody was altering the install location and thus the step had largely become pointless for our end users. Currently you are the first person, out of thousands of users, to request the ability to change the install directory however we always re-evaluate decisions based on feedback. Is there a specific issue you're having with installing to the default directory? Just so you're aware - you can move the directory without having any direct impact on LightSpeed if you need to (however the uninstaller won't know where the files are to uninstall). Thanks for your feedback, John-Daniel Trask |
|
|
Just to clarify - moving the directory only works if you're not installing the designer feature. If you install the designer there will be registry keys that reference the directory. I hope that helps, John-Daniel Trask |
|
|
Thanks for the info.. I could also go into the registry and hack the vsaddin registration to point to the new location... As for your question... regarding why on earth I would want to do so... I'm working with other developers on a project, and we try to use the same "file-system" layout So in essense our dev environment looks the same on Mac/Linux/Windows. This is the part of our little scheme where "c:\Program Files (x86)\Mindscape\LightSpeed 2.0" doesn't play nice... It means that our CI env. needs to know if it's a x86/x64 machine to figure out paths... These are names that don't play along nicely with Linux (I'm not going to have "/Progam Files (x86)" in Linux... :) What we do is everything goes to c:\opt or /opt in Linux / Mac. This way our nant-files / shell scripts can assume the availability of /opt anywhere... |
|
|
That's not a problem: you can copy the DLLs to any location and reference them from there. We do exactly the same thing on our own projects -- we always copy the LightSpeed DLLs to a per-project Lib directory instead of relying on everyone having a copy (let alone the same version) in the same place! Note that if you create a model in a project that doesn't have a reference to LightSpeed, the designer will add references at the Program Files location; but if the project already has the LightSpeed reference (pointing at your c:\opt or project Lib directory) then the designer will respect this and your reference will stand. What you can't do is move the designer stuff (the Tools directory), because of the registry references JD described. But copying the DLLs is definitely fine. |
|