>>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'.
>
>Well, by following the first approach, which is what I tried yesterday and retried again today, it won't work. Even if I don't include any SET CLASSLIB at all, the main class will still get added to the project because in that project I have a sub class of that main class.
The 2nd approach is probably harder to test. Never mind, I just tested it myself, and it also pulls the unwanted stuff in. I guess the Project Manager looks at the Classlibrary property of the class.
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.
