A problem we've run into when we started our migration to Client Access 6.1 is that the version of the IBM.Data.DB2.iSeries assembly went from 10.0.0.0 (with V5R4) to 12.0.0.0 (with V6R1). We immediately started getting messages complaining about not finding the right version of IBM.Data.DB2.iSeries. After we tracked it down to the new version of Client Access, we found that we'd either have to recompile all of the .NET objects that use the database against the new version, or put in binding redirects in the machine.config file. Since we are in a mixed environment, we just set up the binding overrides to make everything pretend it's on 5.4's driver.

John Maassel
Programmer/Analyst
Bob Evans Farms, Inc


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Wills
Sent: Thursday, March 29, 2012 4:29 PM
To: Midrange Systems Technical Discussion
Subject: Re: .NET application iSeries Access requirement???

I should work. We use V5.4 for the driver and the server is at 6.1. The only thing is that later versions of Client Access has more .NET features (I can't recall what is was off the top of my head). But every server/application/desktop needs that uses the .NET program also needs to be upgraded. It's a PITA that we haven't done here yet.

--
Mike Wills
http://mikewills.me


On Thu, Mar 29, 2012 at 3:22 PM, Graap, Kenneth <Kenneth.Graap@xxxxxxxxxxxxx
wrote:

We currently have a home grown .NET application that runs on Win PC
running XP/SP3 and Win 7/SP1 using IBMi Access V5.4 to a Power6
system running IBMi V6.1.1.

We are planning on upgrading our Power6 system to V7.1.

My question is: Does anyone know if the PC configuration mentioned
above will have to be upgraded to a more current IBMi Access release
(like V7.1) or will the .NET application continue to work without
having to upgrade a BUNCH of PC's?

Kenneth
Kenneth E. Graap
503.226.4211 x5537
http://www.linkedin.com/in/kennethgraap

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

________________________________

Notice from Bob Evans Farms, Inc: This e-mail message, including any attachments, may contain confidential information that is intended only for the person or entity to which it is addressed. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and any attachments.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].