Project config out of date?
-
I can compile my project fine, but everytime I go to run my program from within the VS.NET IDE I get the messagebox that says These project configuration(s) are out of date: "ProjectName - Configuration Name" Would you like to build them? It says this for any build config. If I hit yes it'll recompile the resources, relink then start my program. I don't understand why this always happens even after just rebuilding my project. It doesn't happen with all my projects, and I haven't been able to find an option or anything to try changing. Anyone have any ideas? -Lunchy
-
I can compile my project fine, but everytime I go to run my program from within the VS.NET IDE I get the messagebox that says These project configuration(s) are out of date: "ProjectName - Configuration Name" Would you like to build them? It says this for any build config. If I hit yes it'll recompile the resources, relink then start my program. I don't understand why this always happens even after just rebuilding my project. It doesn't happen with all my projects, and I haven't been able to find an option or anything to try changing. Anyone have any ideas? -Lunchy
You'll get that messagebox if a file has been modified since the last compile. So this means one of several things, you have a post-build step that is modifying one of the files (version incrementer?), a virus which is embedding itself in a file once a file has closed, or its just a random bug. Sorry I can't be of more help, James Simplicity Rules!
-
You'll get that messagebox if a file has been modified since the last compile. So this means one of several things, you have a post-build step that is modifying one of the files (version incrementer?), a virus which is embedding itself in a file once a file has closed, or its just a random bug. Sorry I can't be of more help, James Simplicity Rules!
Hrmmm, SourceSafe wouldn't being doing anything would it? I wouldn't think so, but that's the only other thing I could think of. Shouldn't be a version incrementer as I'm not using one. And as far as a virus, I'd think it's a longshot. I've recreated the project and I get the same results. Unless it's attatched to a source file and not a project type file. Maybe it has something to do with wxWindows inards... who knows. :) Thanks much for the reply! :-D -Lunchy
-
Hrmmm, SourceSafe wouldn't being doing anything would it? I wouldn't think so, but that's the only other thing I could think of. Shouldn't be a version incrementer as I'm not using one. And as far as a virus, I'd think it's a longshot. I've recreated the project and I get the same results. Unless it's attatched to a source file and not a project type file. Maybe it has something to do with wxWindows inards... who knows. :) Thanks much for the reply! :-D -Lunchy
SourceSafe might be doing something; but it seems odd. If you create a project not using SourceSafe do you get the same problems? I don't have SourceSafe here so I can't vouch for its innocence. James Simplicity Rules!
-
SourceSafe might be doing something; but it seems odd. If you create a project not using SourceSafe do you get the same problems? I don't have SourceSafe here so I can't vouch for its innocence. James Simplicity Rules!