>>>AFAIR the source is deleted from the memo field copy added into the exe if debug info is excluded, so the comments are gone as well from the exe.
>>
>>That's only for prg files inside the exe, because executable contains only fxp versions. For scx/vcx stuff, look at your executable as text, and you'll see all of your code, comments included.
>
>Nope. Verified with vfp9sp2, changed project options (see bold part above), recompile all and created app in totalcommander-viewer vs previosly compiled app.

With debug info omitted, then yes, the code is gone. The size of the exe is cut by about 30% in my case.

BTW, can't imagine life without TC's viewer. When I say "look at the file", i really mean tc+press f3 :).

>>There's a way to do this - remove all the code (use vcx/replace all methods with ""/pack memo) and build with that (and do that in a set of directories where you'll do this on a copy), and then you'll still have the bloat, but minimized - only your properties and binary memos are in. But then you lose debug info by default - i.e. you may get the stack, but without line numbers, and of course no content of the offending line.
>
>not sure if compile of vcx does not trigger pack as well - at least one of the build GUI actions does...

Yes, it does. I notice the size change when Vault reports it's grown when I want to check in, then just compile classlib, and it goes back. Good diet.