I have been banging my head on this one for a few days and can't seem
to find an answer anywhere.
I have written an app that updates a project's version number in the
assemblyinfo.vb file during the Prebuild event.  With the aid of
pauses in execution, I can see that the version number is, in fact,
getting properly set.  However, when VS2005 actually builds the
project, it uses whatever the old version number was.  However, if I
manually change the value inside VS2005, it builds with the proper
version number.
My question is, are the project files that are about to be compiled
cached prior to any pre-build events being run?
If so, is there any way to clear that and force a recaching after the
prebuild event?
Or, if not, can you think of any other reason why this update would
not hold?

Thank you in advance.
Mike

Update:
In further testing, it seems the process described above does work
when compiling an EXE but fails when compiling a DLL.  The process
used is the same regardless of the project type so I am even more
stumped as to the problem.

app.config and user.config files
Encoding to ISO-8859-1 problems
.NET property names and translation
.NET to x86
What's the new thing after ActiveX?