VS2008 - How to compile 32bit C# app on Vista64?

  • Thread starter Thread starter Figmo
  • Start date Start date
F

Figmo

I have an app that needs to access local MDB files using OLEDB. I
have just upgraded to Vista64 and when I run this app I get a "OLEDB.
4.0 is not registered on local machine" error. From research, I
gather that the Jet drivers are not available for 64 bit apps, but
they do have a 32 bit Jet driver on Vista 64. So the solution I
think is to force compile my assembly as a 32 bit assembly.

But I can't see how to do this. Under my assembly properties, for
Platform I only have "Any CPU". No other options. Which, as I
understand it, means the JIT will run either 32 or 64 bit depending on
the OS it's running under.

This is cool, but doesn't solve my problem. I need to run in 32 bit
mode on a 64 bit OS so I can access the Jet drivers to read my MDB
file.

Is there way I can tell VS 2008 to force compile my assembly as 32
bit?
 
I have an app that needs to access local MDB files using OLEDB.    I
have just upgraded to Vista64 and when I run this app I get a "OLEDB.
4.0 is not registered on local machine" error.   From research, I
gather that the Jet drivers are not available for 64 bit apps, but
they do have a 32 bit Jet driver on Vista 64.   So the solution I
think is to force compile my assembly as a 32 bit assembly.

But I can't see how to do this.   Under my assembly properties, for
Platform I only have "Any CPU".   No other options.  Which, as I
understand it, means the JIT will run either 32 or 64 bit depending on
the OS it's running under.

This is cool, but doesn't solve my problem.  I need to run in 32 bit
mode on a 64 bit OS so I can access the Jet drivers to read my MDB
file.

Is there way I can tell VS 2008 to force compile my assembly as 32
bit?
Click to expand...

The best solution would probably be to go into Configuration Manager,
and create a new
profile (since you may want this one later) and set it up to use X86
instead of "Any CPU".
Then build that profile.

Matt
 
Back
Top