Is msado15.dll different across Windows operating systems?
- From: Chuck Heatherly <chuck.heatherly@xxxxxxxxxxxxxxxx>
- Date: Fri, 08 Sep 2006 12:36:51 -0400
I have several .NET projects that reference the ADODB library on the
fly, meaning they do not use the primary interop library, they
generate the interop version at build time. This is due to the fact
that the projects need to use the most current version of ADODB, and
Microsoft only updates the primary interop library when new versions
of Visual Studio are released. This statement was made by Kevin Yu of
Microsoft in this group in a posting dated 4/7/2005.
I need to run these projects on Windows XP, Windows Server 2003,
Windows XP x64, Windows Server 2003 x64, etc. My question is, can I
just build these projects on a Windows XP box, using the AnyCPU and
x64 platform settings respectively, and then copy the binaries and the
Interop.ADODB file to the desired machine and run there? Or, do I
need to build on the OS in question, so that the platform-specific
copy of msado15.dll is used to generate a platform-specific version of
Interop.ADODB? I.e., is msado15.dll different between all these
operating systems, including Vista? Assuming we are talking about the
same version of ADODB, of course.
Thanks,
Chuck
.
- Follow-Ups:
- RE: Is msado15.dll different across Windows operating systems?
- From: Kevin Yu [MSFT]
- Re: Is msado15.dll different across Windows operating systems?
- From: Ralph
- RE: Is msado15.dll different across Windows operating systems?
- Prev by Date: Re: I can not start this stored procedure?
- Next by Date: Re: Is msado15.dll different across Windows operating systems?
- Previous by thread: How to call an Oracle Stored Procedure that returns REF CURSORS, using ADO from C++
- Next by thread: Re: Is msado15.dll different across Windows operating systems?
- Index(es):
Relevant Pages
|
|