VS 2008 - changes to dialog in the editor not showing up at runtime now!?

Question

0.00/5 (No votes)

See more:

VS2008

Hi all,

Under Window XP, out of the seemingly clear blue sky, a dialog in my C++ project in VS 2008 stopped showing changes to it when saved, compiled and run. I can put static text all over it as a test, here and there, save and compile it and the static text is not there when it is run.

All the other elements from distant past development on this dialog on this machine are indeed there and do work.

What's stranger is the fact that if I boot to the Windows 7 x64 partition on this computer (dual boot) and run VS 2008 opening the solution (same target) there, the changes made are visible and also show up at runtime in Win 7. Canging the dialog in the VS 2008 on the Win7 side works and shows updates made as expected.

I used to only do dev in XP on this machine. Withing the last year I set up the dual boot for parallel x86 / x64 debugging of this project that is now in beta.

The changes to the dialog made in Win7 don't show up if rebuilt on vs 2008 on the XP side. This was my first indication that something was wrong.

I have cleaned the project on the XP side to no avail

HELP! :-)

Posted 13-Jun-13 5:54am

Ron Anders

Add a Solution

Comments

Richard MacCutchan 13-Jun-13 12:07pm

You probably have some bad file links in your project. Check that the source files in your project are linked to the correct files on your disk, i.e in the actual project directory. It may actually pay you to delete them from the project (but not from disk) and then add them back in, ensuring that you add from the correct location. Then try clean and rebuild.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Matthew Faithfull · Accepted Answer · 2013-06-13T06:06:00

It does sound like the XP side is running an old copy of the .exe or loading and old copy of the .dll which is more likely. You don't mention exactly what module your dialog is being compiled into. I would search for duplicates of that by name in case one is being loaded from the wrong place.

This could also possibly be an example of the failed linker bugs that can occur when the underlying compiler is changed in Visual Studio. Going from VS2008 to VS2010 I had issues where 2008 was trying to use the newer compiler and linker and it would all claim to be working but alternately produce garbage linker errors or claim success but fail to actually write the executable. Cleaning did not work in these circumstances even though it said it succeeded and vaguely sensible errors only started showing up when the entire output directory was deleted.