When I use a post-build with my web project (which has an associated Silverlight 3 project in the solution, and uses a web service to access the DB), I get some really weird results. The post-build event creates a zip file from the published folder and uploads it, among other things. However, it doesn't seem to matter, because I seem to get this result regardless of what is in the post-build step.
Often (but maybe not always) the results in the resulting zip file were one release old, as if the zip file were created before the actual build. However on further investigation it turns out that the actual output files were a version old, almost as if the build step were never run. As best I can tell, it doesn't matter what is in the post-build event -- it's very existence causes the published output to be wrong. This happens even if I manually delete the contents of the output folder before I publish. Adding a pre-build event, with no post-build event also causes this to happen. Everything is fine if I remove the pre- and post-build events and run them manually from .bat files.
In short, even the existence of a pre- or post-build event seems to cause VS to create files that are one version old.
Has anyone seen anything like this, or have any ideas?