Re: .NET Data Provider

Elvis,

No I have not. But I have done this with other apps. Check out the
GACUTIL http://msdn.microsoft.com/en-us/library/ex0ss12c(VS.80).aspx.

Chris

-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Elvis Budimlic
Sent: Friday, May 01, 2009 10:12 AM
To: '.net use with the System i'
Subject: Re: [SystemiDotNet] .NET Data Provider

Interesting.
Have you used this method to distribute a .net application using IBM's
provider to a 'virgin' PC (i.e. no Client Access installed)?

Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com

-----Original Message-----
Subject: Re: [SystemiDotNet] .NET Data Provider

I don't think they do. This is a pretty standard way of obtaining
references and code that are used in any un-obfuscated .NET assembly.
If you use the Windows Command Line to navigate to
"c:\windows\assembly\gac", you can copy the IBM.Data.DB2.* folder
contents somewhere else. Then download
http://www.red-gate.com/products/reflector/ and open the copied IBM .NET
assembly with Reflector. You can view the disassembled code as well as
any references and base types used in the assembly.

-----Original Message-----
Subject: Re: [SystemiDotNet] .NET Data Provider

Does IBM document this somewhere?

Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com


-----Original Message-----
Subject: Re: [SystemiDotNet] .NET Data Provider

I just pulled the 1.0 assembly from GAC and taking a look in Reflector.

References:
* Advapi32
* Cwbcore.dll
* Cwbcore.Dll
* Cwbdc
* Kernel32



-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Walden H.
Leverich
Sent: Thursday, April 30, 2009 4:41 PM
To: .net use with the System i
Subject: Re: [SystemiDotNet] .NET Data Provider

I don't believe that's the case. The .NET DLL then invokes non-.net DLLs
(CWBxxx) to do the actual communication. It's not a "pure" .net
assembly. I've never tried to bundle all the DLLs together, certainly
not going to be a supported setup.

-Walden