[Solved?] VS2008 clean & rebuild breaks dodataexchange only under xp?

Question

0.00/5 (No votes)

See more:

Oh this isn't fair / I should have just let it be.

Environment:

XP / Win7 32 bit dual boot laptop
Source code folder common to both OS's as a local driver map on yet a 3rd partition.

The project is a com dll plugin to a commercial 3rd party host application that I don't have the source for. The dll plugin has a property page that the host app activates when a menu is clicked on the host application menu. There is no ONInitDialog() in the property page, just Activate() and Show().

Recently I got the idea that a tabbed interface on the property page would be better than the one page messy thing it is today. I ran into problem after problem with what I have surmised was modeless dialog launching modeless dialogs. This is speculation only as I just don't know.

After 4 tries, and reverting changes from the repository, I have given up for now but have been left with my XP setup damaged.

I can clean the solution, or clean the project and rebuild the solution or project under the windows 7 32 bit boot partition and have the property page launch. But if I dare do the same under the XP partition (home sweet home) then the DoDataExchange() finds that the hWnds for all the controls on the property page are NULL. (Internet says that means they are not created yet).

Ok, but if I then boot into Win7 and rebuild (clean or otherwise) it runs fine and then will run fine in XP too, until I dare do a clean again in XP. The image will then be broken until I rebuild it under windows 7.

I have an image of the XP from last month before all this silliness began that I can restore, but a finer fix would both serve me going forward and be less traumatic.

Thanks for reading.

:Ron

Posted 1-Jun-15 3:48am

Ron Anders

Updated 3-Jun-15 3:02am

v2

Add a Solution

Comments

Philippe Mori 1-Jun-15 12:49pm

Reinstall Visual Studio or the OS if you have break it up. If things doesnot works as expected, this is probably the best thing to do. Your system is probably corrupted.

KarstenK 1-Jun-15 13:25pm

My tip is a security issue in the used COM-objects. Check whether the are all registered an working. Test it as admin or with UAC disabled.

Ron Anders 1-Jun-15 13:28pm

UAC in XP.

Cool.

Albert Holguin 1-Jun-15 15:06pm

This just about sounds like a permissions problem. I'd check build directory permissions, resource file(s) permissions... ??? ... worth checking out.

Ron Anders 1-Jun-15 18:17pm

I am restoring my Acronis backup to yet another drive to make sure that A: the image is sane and B: the xp will clean n' build like I think it did before.

I won't be doing anything dangerous until tomorrow or next week because tomorrow is another darn full moon. What should work generally doesn't for me on the full monn or for two days following.

barneyman 1-Jun-15 19:50pm

the registration of the COM element would be the first thing to investigate ... regsvr32 should be done as a post build step

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)

Ron Anders · Answer 1 · 2015-06-03T03:01:00

Well, that was special.

As for those who have suggested re-registering the COM component, I'm sorry I neglected to say that the property page is not separate, but an integral part of the COM plugin dll which is running, and therefore happily registered.

I backed up the most recent code base and restored the image backup from a month ago and now xp install is cleaning / rebuilding and running without the DoDataExhange() crashes. Even after restoring the latest code base with all the bug fixes for the month of May but no tabs.

Thanks for participating in this bit of fun.