Hi Michel,
Having read your thread, I hope I now have some grip on your specific problem, that is indeed linked to the core subject of this thread.
Two possible strategies come to my mind:
Do what Walter Meester proposed: Re: New stuff gets included Thread #960731 Message #960960
Do what I do (although in practice I always pull classes in, included): Re: New stuff gets included Thread #960731 Message #961752
Both strategies should prevent that the main classlib gets pulled in or even 'known'.
Hope this helps.
>>Here's a situation that regularly causes a problem.
>>
>>When rebuilding, a new program, vcx, whatever gets included if it can be located, without any warning and it's not always 'obvious' to me that it happened. But inclusion is not always what I want. Instead, I more frequently want it pulled in as excluded. I have one exe and several apps. Certain routines are included in the exe and must not be included in the apps. If such a routine gets included in an app, it will be a second instance and it may differ from the official one in the exe, because version updates often only include one or two apps. Problems may and will arise.
>>
>>Does this sound familiar?
>>Who has worked out a solution to this unwanted behavior?
>
>I have an ongoing thread with an unresolved issue. That deals pretty much exactly as yours. This is thread #961179. My setup consists of one EXE which contains all the classes and some sub EXEs. The main EXE runs all the time and will call the related sub EXE on request. Those sub EXE may have their own classes. So far so good, as long as I don't subclass a class from the main EXE, I am ok. But, this weekend, I wanted to upgrade my interface and subclassed some classes from the main EXE into one sub EXE. So, as you said, on the next compile, it automatically added the reference of the main class in the project. Also, as you said, I don't want it in there for version control. So, I marked it as excluded. The problem with that is the following:
>
>No matter what I try, there will now be always a reference to the main class in the sub EXE either as included in the project or excluded. Right now, it is excluded. This causes my sub EXE to look on the disk for the VCX which it will not find on the server and will generate an error at run time saying that the class cannot be found. If this stupid reference wouldn't be added to the project, I wouldn't run into this error as the sub EXE would be able to take the reference of the main class from the main EXE and the program would run ok.
>
>This is where I am right now. I cannot proceed with the new interface because of that stupid reference which keeps getting added to the project as soon as I compile.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
