AccessFromDotNet: Difference between revisions
From Pickwiki
Jump to navigationJump to search
updated PDP.NET and mv.NET info, add "see also" |
m link fix |
||
| Line 11: | Line 11: | ||
IBM purchased a license to the source for an old release of mv.NET and has rebranded it for distribution as a U2-only product. | IBM purchased a license to the source for an old release of mv.NET and has rebranded it for distribution as a U2-only product. | ||
See also: CreateWebInterfaces | See also: [[CreateWebInterfaces]] | ||
---- | ---- | ||
| Line 17: | Line 17: | ||
:I would recommend looking at using [http://support.microsoft.com/default.aspx?scid=kb;en-us;308672 Microsoft Enterprise Services] to manage connection pooling and expose a useful interface to non-U2 developers. We have used Enterprise Services and XML in/out of U2 with excellent results. | :I would recommend looking at using [http://support.microsoft.com/default.aspx?scid=kb;en-us;308672 Microsoft Enterprise Services] to manage connection pooling and expose a useful interface to non-U2 developers. We have used Enterprise Services and XML in/out of U2 with excellent results. | ||
:Something like [http://www-306.ibm.com/software/data/u2/redback/ RedBack RBOs] also provide a neat interface into U2, Graphical mapping provides an opportunity to present that old, hacked application to Windows developers with a nice clean object-oriented skin. | :Something like [http://www-306.ibm.com/software/data/u2/redback/ [[RedBack]] RBOs] also provide a neat interface into U2, Graphical mapping provides an opportunity to present that old, hacked application to Windows developers with a nice clean object-oriented skin. | ||
:Also recommend looking at [http://msdn.microsoft.com/practices MSDN Patterns and Practices] for some very good guides on how to do this stuff. | :Also recommend looking at [http://msdn.microsoft.com/practices MSDN Patterns and Practices] for some very good guides on how to do this stuff. | ||
Latest revision as of 23:48, 26 February 2015
Information on connecting to U2 from .NET
There's a whitepaper on IBM's site about U2 and .NET: ftp://ftp.software.ibm.com/software/data/u2/pubs/whitepapers/ibmu2-microsoftnet.pdf
You can use jbimp.exe (usually in Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin) to convert java bytecode into a .net assembly.
Link to Raining Data's .NET data provider:
http://www.rainingdata.com/products/connect/dotnet/index.html
Raining Data no longer sells or supports the PDP.NET product. See mv.NET.
IBM purchased a license to the source for an old release of mv.NET and has rebranded it for distribution as a U2-only product.
See also: CreateWebInterfaces
2006-01-03
- I would recommend looking at using Microsoft Enterprise Services to manage connection pooling and expose a useful interface to non-U2 developers. We have used Enterprise Services and XML in/out of U2 with excellent results.
- Something like RedBack RBOs also provide a neat interface into U2, Graphical mapping provides an opportunity to present that old, hacked application to Windows developers with a nice clean object-oriented skin.
- Also recommend looking at MSDN Patterns and Practices for some very good guides on how to do this stuff.
