OK, so is it just the version number that gets cached, or the whole exe definition. My current experience says that I can recompile and re-run an exe and the changes I made in that session (except the version number, which I haven't checked) will be seen.
Is that what you're saying?
Cheers,
Andrew
>Sorry for the confusion.
>
>I was reconfirming your results. If you have a project, compile it, then run the exe (with VFP still running), you will see version "X". If you make changes, recompile, and run the exe (with VFP still running), the version number will not change until you kill VFP and run the exe in it's own process or another process of VFP.
>
>Dave
>
>>Dave, can you clarify this please. Do I need to clear memory before doing a second recompile? I'm not really sure what you're saying here.
>>
>>>Versioning resides in memory of the current VFP session.
If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?
From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."
All my FoxTalk and other articles are available on my
web site.
Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.
