I have a project class in my project to make use
of project hooks when I do builds. I always check
the "recompile all files" option, so I receive a
"File proj_lib.vcx is in use and cannot be recomiled"
message whenever I build. This is not a real big
deal, I just hit the ignore button. But I was
wondering if there was an easy way to avoid this and
still do a "recompile all files".

I've tried variations on use of the CLEAR command,
but can't find anything that yields an error-free
build. I suspect it's all in the timing of things
since I have a good chunk of code that runs whenever
a build is done (forms run to collect build details,
tables are updated, printer info cleared from reports,
etc). Any insights?

-- TRW
_______________________________________
t i m . w i t o r t
_______________________________________

Re: Building with a project class by Olaf

Olaf
Mon Jun 09 14:55:26 CDT 2008

You don't need to make the project hook classlib
part of the project. And you should not.

Bye, Olaf.

Re: Building with a project class by tim_witort

tim_witort
Wed Jun 11 11:16:50 CDT 2008

Olaf Doschke seemed to utter in news:59207178-07EA-461D-B20D-8E4D08EA2DA9
@microsoft.com:

> You don't need to make the project hook classlib
> part of the project. And you should not.
>
> Bye, Olaf.
>

That's funny. This project has been in use and maintained
for over 5 years and I never thought to remove the project
class from the project. In my mind, it needed to be in
the project to work correctly, but since the project
settings point to the class, it doesn't need to be
included in the project itself.

Works fine now. Thanks Olaf.

-- TRW
_______________________________________
t i m . w i t o r t
_______________________________________

Re: Building with a project class by Olaf

Olaf
Wed Jun 11 11:45:18 CDT 2008

> That's funny. This project has been in use and maintained
> for over 5 years and I never thought to remove the project
> class from the project.

It took me a while too, to get that idea.
It's also tempting to have the project hook
as a part of the project, to make changes.

But as soon as its bugfree and complete,
there's no reason to keep it in the project
more than in the project information.

Also look at the "Multiple ProjektHooks"
hook from Greg Reichert and the list of
project hooks he maintains here:

http://www.glrsoftware.com/download.asp

I have tried few so far, but there are many
ideas in there...

Bye, Olaf.