Hi all, I'm having a problem with this and haven't found an answer in
these groups or the Preemptive FAQ.
I have an assembly from my main project that is dotfuscated (CE
version) as a post-build event. This all works fine. However, my
deployement (setup) project takes the primary output from the main
project and the setup build therefore rebuilds the main project
overwriting the dotfuscated version. Looking at these NGs, this is
expected behaviour.
The only fix for this is, as I have read, to include the dotfuscated
file (rather than the primary output) in the setup project. This is OK
but with one problem: I then lose the ability to differentiate between
Release and Debug builds because the file include option has no
understanding of (Active), AFAICT.
Is there a way around this that anyone knows?
TIA
Mark
these groups or the Preemptive FAQ.
I have an assembly from my main project that is dotfuscated (CE
version) as a post-build event. This all works fine. However, my
deployement (setup) project takes the primary output from the main
project and the setup build therefore rebuilds the main project
overwriting the dotfuscated version. Looking at these NGs, this is
expected behaviour.
The only fix for this is, as I have read, to include the dotfuscated
file (rather than the primary output) in the setup project. This is OK
but with one problem: I then lose the ability to differentiate between
Release and Debug builds because the file include option has no
understanding of (Active), AFAICT.
Is there a way around this that anyone knows?
TIA
Mark