>Peter,
>
>
>Sorry that I disagree, it is VFP's problem. (You seem to suggest that I am the problem. However, I never said that I use extensive classlibraries. On the contrary, mine are all quite dedicated.)
>>
>>The problem already happens if only one program file refers to one other program file.>
>Then exchange classlib for program file in my previous message. It's still your problem from not having your program files granular enough.
Once more: The problem already happens if only one program file refers to one other program file. How granular can one make it?!
>
>It should be my decision whether or not that second file should be included and how it should be included. I have never asked the vfpteam to let vfp always automatically include it. I guess they expect me to thank them for the service, but must conclude that they don't offer a semi-automatic service. Suppose I would not give the users of my applications the opportunity to cancel their changes ("The changes will be saved. Are you sure?"), nobody would hire me.>
>You needn't have ever asked for this project inclusion process, it has always worked like this.
>
>You do have a chance to overcome your packaging issues by marking the pulled in files as excluded from the project.
Do you really think that I don't know this all? I work with foxpro since 1990.
>
>Having said that, I know there is a way to make it semi-automatic: Use a project manager hook. My question was: Has anybody implemented one?>
>How would a project hook, know which files it should include as normal and which ones are your special case files that aren't really needed?
There are some hooks that can be helpful: BeforeBuild and AfterBuild. Furthermore, there is the Files collection. Launch a form that shows the to-be-added files, let the user make some decisions and we might undo some changes. I guess I can construct it all myself, but I have the feeling that someone else might already have done so. That's what I am trying to find out here.
>In the long run I think you'll be better off examining your code packaging.
Don't think so...
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.
