Re: Copying projects

Tech-Archive recommends: Fix windows errors by optimizing your registry

I use this method a lot as well. In fact, if you separate the resources
into an external DLL you can even have separate menus, dialogs, etc. based
on the code version that is loaded. I've found that the biggest problem,
for me, with multiple versions is trying to keep all the files up to date.
So, if you are going this route you really need to have a common code base
to share between the programs and only have the UI stuff differ.

Tom

"David Wilkinson" <no-reply@xxxxxxxxxxxx> wrote in message
news:eRckjNEVGHA.4772@xxxxxxxxxxxxxxxxxxxxxxx
R.Kaiser wrote:

Ajay Kalra schrieb:

Instead of having two projects, why not simply change the title of the
form at run time based on some setting. You should do your best to
avoid maintaining more code. In this case, you are going to be stuck
with making changes in both projects as the project moves along. Its a
big no-no.

---
Ajay


Sure, this would be the best. But I need the titles etc. in the source
code for demonstration purposes.

Thanks
Richard

Richard:

My application has two versions, one of which is a "lite" version of the
other. I just have two different builds of the program. The differences
are controlled by a preprocessor symbol, like so

bool CMyApp::IsLite() const
{
#ifdef LITE
return true;
#else
return false;
#endif
}

The two versions appear to be different programs, but the two binaries are
99% identical.

David Wilkinson


.