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
|
I notice that in the screencasts you do not add a reference explicitly, rather you add a LightSpeed model file, this adds the references. When I look at these references I notice the path to them is c:\ProgramFiles (x86)\Mindscape\LightSpeed...etc. When I want to add a reference I have to browse for it, it does not come up in the .NET tab of the add references dialog. Why not? I don't like it, the reason that I noticed this is that I downloaded the DistributedExample (from another post on this forum) and the references were all missing and I have had to go and fix them. Something that I don't think I would have had to do if they were in the GAC etc. Won't stop me developing, but would like to know the reason, have I installed incorrectly? |
|
|
No, you haven't installed incorrectly. Our customers tend to work in one of two ways, and neither benefits from us putting LightSpeed into the Add References dialog: (1) Some customers prefer to source-control their dependencies, and therefore copy the LightSpeed DLLs to a source-controlled location alongside the project. This ensures that everyone is using the same version of the DLLs, that the correct version of the DLLs is guaranteed to be used on the build server, etc. at the cost of having to re-copy the DLLs every time you upgrade. For these customers, putting the Program Files path into Add References would be unhelpful because they don't want to use the Program Files path. (2) Other customers prefer the convenience of having the reference automatically added for them and not having to worry about having the DLLs in two places. For these customers, putting LightSpeed into Add References would be irrelevant because they just let the designer add the reference for them. We don't install in the GAC because we want users to default to xcopy deployment of LightSpeed. If we installed into the GAC, Visual Studio would by default not copy the LightSpeed DLLs to the output directory, so customers wouldn't have all the files their app needed in one place. Hope this clarifies the reasoning! |
|