>>Hi All,
>>
>>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?
>
>Use a global Project for development
>define a exe project => compile EXE
>define various app projects => compile APP

For each application I have several 'projects'. One of them is for the exe, the others for the apps. Some apps are even used in several applications. (I purposely put the word 'project' between quotes, because, for me, they are better described by the word modules.)

My projects/modules reside in separate maps and when building I guarantee that the path - set('path') - does not point to stuff that should not be included. This structure prevents that unwanted stuff gets included.

However, one legacy application is not structured in this way and the problem I described only occurs in that applications' environment.

>Or: Use a projectHook.beforeBuild for customize the Build process

Yes, probably I should code somewhere in a project manager hook. Who has worked out a solution using a project manager hook?