v2005 vs. v2008 Configuration settings

[=?Utf-8?B?amM=?=]

Hello,

I am able to successfully compile/link/and execute my v2005 applications using
v2008 (after the v2008 automatically converts the v2005 configurations
settings).

I created a "generic" v2008 app wizard program. I changed the configuration
settings of the new v2008 to match the "generic" app wizard configuration
settings. The applications compile/link OK, but the programs do not execute
correctly.

Instead of using trial and error to try and identify which setting(s) are
causing
the problem. Does anyone know what configuration setting(s) could possibly be
causing the execution problems?

Thanks,
-jc

[David Lowndes]

>I created a "generic" v2008 app wizard program. I changed the configuration

>settings of the new v2008 to match the "generic" app wizard configuration
settings. The applications compile/link OK, but the programs do not execute
correctly.

Did you try building & running before changing the settings? Did that
work?

Which settings have you changed?

When you say it doesn't execute correctly, what precisely do you mean
- does it start, crash, or something else?

Dave

[=?Utf-8?B?amM=?=]

"David Lowndes" wrote:

I created a "generic" v2008 app wizard program. I changed the configuration
settings of the new v2008 to match the "generic" app wizard configuration
settings. The applications compile/link OK, but the programs do not execute
correctly.

Did you try building & running before changing the settings? Did that
work?

Which settings have you changed?

When you say it doesn't execute correctly, what precisely do you mean
- does it start, crash, or something else?

Dave

Dave,

Thank you for replying to my posting. I apologize for the confusion, you
asked if I compiled/linked and executed the program before I changed the
settings. Yes, I was able to successfully compile/link and execute the
program before I changed the settings. The execution problems occured after I
changed the settings.

I know when I stated the program did not execute correctly, that might also
cause some confusion. The program does start and does not crash. There is
part of the application that just does not execute. Actually, it took me a
couple of days before I realized that part of program was not executing. I
tested the main part of the program, and just assumed that the rest of
program was running OK.

Thanks,
-jc

[PvdG42]

"jc" <[e-mail] in message
news:14**********************************@microsof t.com...

>

Thank you for replying to my posting. I apologize for the confusion, you
asked if I compiled/linked and executed the program before I changed the
settings. Yes, I was able to successfully compile/link and execute the
program before I changed the settings. The execution problems occured
after I
changed the settings.

I know when I stated the program did not execute correctly, that might
also
cause some confusion. The program does start and does not crash. There is
part of the application that just does not execute. Actually, it took me a
couple of days before I realized that part of program was not executing. I
tested the main part of the program, and just assumed that the rest of
program was running OK.

Thanks,
-jc

Did the specific part of the program that now misbehaves execute correctly
before you changed configuration settings? If so, do what David suggested
and change them back.
If you don't recall which settings you changed, you can take a shot at this:

Tools->Import and Export Settings->Select "Reset All Settings", then save
your current settings or don't as you see fit.->Select the Default
Collection of Settings you had previously. That should put you back at
default.

If that doesn't work, and you kept a backup copy of the VS 2005 project, you
may have to uninstall VS 2008, and physically delete an files left in the
install folder, then reinstall. Then convert your backup using the defaults.

[David Lowndes]

>I know when I stated the program did not execute correctly, that might also

>cause some confusion. The program does start and does not crash. There is
part of the application that just does not execute.

Why, what's special about that aspect - does it interface to a DLL by
any chance?

Have you tried debugging it to find what's going wrong?

Dave

[=?Utf-8?B?amM=?=]

"David Lowndes" wrote:

I know when I stated the program did not execute correctly, that might also
cause some confusion. The program does start and does not crash. There is
part of the application that just does not execute.

Why, what's special about that aspect - does it interface to a DLL by
any chance?

Have you tried debugging it to find what's going wrong?

Dave

Yes, the part of the application that does not execute does interface to a
DLL.

Thank you for taking the time to respond to my posting. I have found a backup
copy of the previous v2005 settings, and I am now using the old settings and
the
program is running OK.

Thanks again,
-ic

[Ben Voigt [C++ MVP]]

jc wrote:

"David Lowndes" wrote:

>>I know when I stated the program did not execute correctly, that
might also cause some confusion. The program does start and does
not crash. There is part of the application that just does not
execute.

Why, what's special about that aspect - does it interface to a DLL by
any chance?

Have you tried debugging it to find what's going wrong?

Dave

Yes, the part of the application that does not execute does interface
to a DLL.

Are you running on a 64-bit version of Windows by any chance?

>
Thank you for taking the time to respond to my posting. I have found
a backup copy of the previous v2005 settings, and I am now using the
old settings and the
program is running OK.

Thanks again,
-ic

[=?Utf-8?B?amM=?=]

"Ben Voigt [C++ MVP]" wrote:

jc wrote:

"David Lowndes" wrote:

>I know when I stated the program did not execute correctly, that
might also cause some confusion. The program does start and does
not crash. There is part of the application that just does not
execute.

Why, what's special about that aspect - does it interface to a DLL by
any chance?

Have you tried debugging it to find what's going wrong?

Dave

Yes, the part of the application that does not execute does interface
to a DLL.

Are you running on a 64-bit version of Windows by any chance?

Thank you for taking the time to respond to my posting. I have found
a backup copy of the previous v2005 settings, and I am now using the
old settings and the
program is running OK.

Thanks again,
-ic

Hello Ben,

Yes, I am running on a dual-core AMD64, 2GB memory, 1/2 TB disk, WinXP(x64).

-jc

[Ben Voigt [C++ MVP]]

jc wrote:

"Ben Voigt [C++ MVP]" wrote:

>jc wrote:

>>"David Lowndes" wrote:

I know when I stated the program did not execute correctly, that
might also cause some confusion. The program does start and does
not crash. There is part of the application that just does not
execute.

Why, what's special about that aspect - does it interface to a DLL
by any chance?

Have you tried debugging it to find what's going wrong?

Dave
Yes, the part of the application that does not execute does
interface to a DLL.

Are you running on a 64-bit version of Windows by any chance?

>>>
Thank you for taking the time to respond to my posting. I have found
a backup copy of the previous v2005 settings, and I am now using the
old settings and the
program is running OK.

Thanks again,
-ic

Hello Ben,

Yes, I am running on a dual-core AMD64, 2GB memory, 1/2 TB disk,
WinXP(x64).

You can't load 32-bit DLLs into a 64-bit process. Make sure the main .NET
executable is marked as "X86", not "Any CPU".

>
-jc

[=?Utf-8?B?amM=?=]

Hi Ben,

Thank you for replying to my posting.

I apologize, for the confusion, concerning
my development environment. I am running
WinXP(x64), but I am developing a 32-bit
application. I am aware that you cannot
load a 32-bit dll into a 64-bit process.

-jc

"Ben Voigt [C++ MVP]" wrote:

jc wrote:

"Ben Voigt [C++ MVP]" wrote:

jc wrote:
"David Lowndes" wrote:

I know when I stated the program did not execute correctly, that
might also cause some confusion. The program does start and does
not crash. There is part of the application that just does not
execute.

Why, what's special about that aspect - does it interface to a DLL
by any chance?

Have you tried debugging it to find what's going wrong?

Dave
Yes, the part of the application that does not execute does
interface to a DLL.

Are you running on a 64-bit version of Windows by any chance?
Thank you for taking the time to respond to my posting. I have found
a backup copy of the previous v2005 settings, and I am now using the
old settings and the
program is running OK.

Thanks again,
-ic

Hello Ben,

Yes, I am running on a dual-core AMD64, 2GB memory, 1/2 TB disk,
WinXP(x64).

You can't load 32-bit DLLs into a 64-bit process. Make sure the main .NET
executable is marked as "X86", not "Any CPU".

Hello

>

[Ben Voigt [C++ MVP]]

jc wrote:

Hi Ben,

Thank you for replying to my posting.

I apologize, for the confusion, concerning
my development environment. I am running
WinXP(x64), but I am developing a 32-bit
application. I am aware that you cannot
load a 32-bit dll into a 64-bit process.

-jc

Yeah, but I'm guessing the non-working project settings aren't generating
the 32-bit executables you want.

>
"Ben Voigt [C++ MVP]" wrote:

>jc wrote:

>>"Ben Voigt [C++ MVP]" wrote:

jc wrote:
"David Lowndes" wrote:
>
>>I know when I stated the program did not execute correctly, that
>>might also cause some confusion. The program does start and
>>does not crash. There is part of the application that just does
>>not execute.
>>
>Why, what's special about that aspect - does it interface to a
>DLL by any chance?
>>
>Have you tried debugging it to find what's going wrong?
>>
>Dave
>>
>
Yes, the part of the application that does not execute does
interface to a DLL.

Are you running on a 64-bit version of Windows by any chance?

>
Thank you for taking the time to respond to my posting. I have
found a backup copy of the previous v2005 settings, and I am now
using the old settings and the
program is running OK.
>
Thanks again,
-ic

Hello Ben,

Yes, I am running on a dual-core AMD64, 2GB memory, 1/2 TB disk,
WinXP(x64).

You can't load 32-bit DLLs into a 64-bit process. Make sure the
main .NET executable is marked as "X86", not "Any CPU".

Hello