VS2005: Win64 build mode : project properties 'operation could not be completed'

[Egbert Nierop \(MVP for IIS\)]

Hello,

I created a Win64 build environment by copying from a Win32 environment, and
modifying the Win32 macro to the Win64 macro.

After that, the properties window does not load anymore and building or
rebuilding does not work anymore.

On one computer, which is a slightly newer install it does work.

I'm trying to figure how to solve this. Who has an idea?

Regards

[David Lowndes]

>I created a Win64 build environment by copying from a Win32 environment, and

modifying the Win32 macro to the Win64 macro.
What precisely did you change?
After that, the properties window does not load anymore and building or
rebuilding does not work anymore.
When you say building doesn't work, what happens - anything, or do you
get errors?
On one computer, which is a slightly newer install it does work.

If it's the same project/solution, that would indicate something on
the other machine has been corrupted. Have you tried doing a repair
installation on the affected machine?

Dave

[Egbert Nierop \(MVP for IIS\)]

"David Lowndes" <Da****@example.invalid> wrote in message
news:gm********************************@4ax.com...

I created a Win64 build environment by copying from a Win32 environment,
and
modifying the Win32 macro to the Win64 macro.

What precisely did you change?

Only the WIN32 macro, has been modified to WIN64. Further on, all settings
seemed OK.

After that, the properties window does not load anymore and building or
rebuilding does not work anymore.

When you say building doesn't work, what happens - anything, or do you
get errors?

Nothing. It displays the resume as if it did compile, but it did not display
progress etc. When I deleted all the output files, it does not rebuild the
files.

On one computer, which is a slightly newer install it does work.

If it's the same project/solution, that would indicate something on
the other machine has been corrupted. Have you tried doing a repair
installation on the affected machine?

Not yet.