AccessFromDotNet: Difference between revisions

From Pickwiki
Jump to navigationJump to search
Stuboy (talk | contribs)
mNo edit summary
 
TonyG (talk | contribs)
updated PDP.NET and mv.NET info, add "see also"
Line 7: Line 7:


Link to Raining Data's .NET data provider:
Link to Raining Data's .NET data provider:
http://www.rainingdata.com/products/connect/dotnet/index.html
http://www.rainingdata.com/products/connect/dotnet/index.html<br>
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


----
----

Revision as of 11:08, 17 January 2009

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.