Sunday, February 19, 2012

ADO Interop Access under Vista

I am trying to load a

project under VS2005 under Windows Vista that references an ADOX

wrapper that is looking for version 2.8.0.0. The reference fails

because the library is not registered.

I thought maybe

installing MDAC 2.8 would solve my problems, but when I run the

installer for that, it briefly puts up a dialog that it is extracting

files, then it disappears.

Anyone have any ideas?

--Bruce
Hi,

I would suggest that you look under "Deployment Projects" on MSDN

Here you can choose "Prerequisites" for you application which get installed through an installer.

I had a quick look but as I dont know what language you are using I can only suggest the above.

Regards,
Pace
|||This is not a deployment issue, this is a build issue.

This is an existing C# solution that I am trying to build under VS2005 under Windows Vista. One of the projects references a .NET wrapper around ADOX. When the project loads in VS2005, I get the warning sign over the reference indicating it can't resolve the reference, and I get 'type not registered' errors.

This is a fresh install of Vista RTM and Visual Studio. The project existed before and builds fine under Windows XP.

The properties on the reference refer to v2.8.0.0. Perhaps Vista doesn't have/support this version of MDAC?

When I try to install v2.8 of MDAC under Vista, the installer starts but then abruptly aborts.|||

I actually came across the exact same problem last night with a project that I started in XP and then tried to open in Vista.

I suspect that you are right -- ADOX exists on Vista, but it is version 6.0.6000.16386. I would try removing the reference to ADOX and then adding it back in again with the 6.00 version and see if that solves your problem.

Also, you MIGHT be able to take the 2.8 version from XP -- C:\Program Files\Common Files\System\ado [I believe it is msadox.dll] and copy it to Vista and register it? I haven't tried that so I don't know if it will/won't work.

I'm going to do some additional work on this tonight to see if I can come up with a solution; if you find something, please post!

No comments:

Post a Comment