I have a solution in VB.Net Visual Studio 2010.
It is a small service program and installer.
It was originally written to compile as 'Any CPU'.
It works fine on a Windows 2003 server.
However the server will be upgraded at somepoint in the year and I will need it to run as 'X86' when the server upgrades
because there are connection strings I need to use that are 32 bit.
I have therefore changed the solution in Visual Studio to compile as 'x86'. It creates a new folder in the solution that is called x86 with a new 'Release' and 'Debug' folder holding the compiled programs. It does not however create a new installer executable when I rebuild the solution. The installer continues to install the old 'Release' and 'Debug' folder details from the last 'Any CPU' compile.
So.....How can I get the installer to install the X86 executables instead of the 'Any CPU' executables?
Dazed and confused.
Remember.. 'Depression is just anger without enthusiasum'.
It is a small service program and installer.
It was originally written to compile as 'Any CPU'.
It works fine on a Windows 2003 server.
However the server will be upgraded at somepoint in the year and I will need it to run as 'X86' when the server upgrades
because there are connection strings I need to use that are 32 bit.
I have therefore changed the solution in Visual Studio to compile as 'x86'. It creates a new folder in the solution that is called x86 with a new 'Release' and 'Debug' folder holding the compiled programs. It does not however create a new installer executable when I rebuild the solution. The installer continues to install the old 'Release' and 'Debug' folder details from the last 'Any CPU' compile.
So.....How can I get the installer to install the X86 executables instead of the 'Any CPU' executables?
Dazed and confused.
Remember.. 'Depression is just anger without enthusiasum'.
