![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
Ok, the further I get into SOAP the more frustrated I am getting ![]() .... Can someone PLEASE point me in a some direction? ... Dean Harry |
#3
| |||
| |||
|
Ok, the further I get into SOAP the more frustrated I am getting ![]() ... Can someone PLEASE point me in a some direction? ... Dean Harry [ad] Dean, I know some people get tired of me mentioning mv.NET when notes like this come up, but the fact is that 1) I used to encounter platform-specific issues with comms, 2) then I started using mv.NET, 3) and now I no longer have such issues. *How tough is that? *These days I focus on apps and not comms (unless I'm writing custom socket interfaces on-contract). We have a few clients who have beat their heads against the UO / U2 SOAP/XML walls, and then they found relatively quick relief with an mv.NET solution. So to get you to this point, check this out: remove.pleaseNebula-RnD.com/products/mvdotnet and at this next link you'll find a video showing web services client/server with C# and no messing with SOAP or XML at all: remove.pleaseNebula-RnD.com/products/gallery.htm Note from the video that you really could use UO.NET for this interface. *The take-away is that it's Much easier to use .NET web services and related helpers than to mess with SOAP and platform-specific comms in any given DBMS. Now, you mention MonoDevelop: if you're using Mono you will not be able to use mv.NET or UO.NET because these are built with Microsoft .NET, not Mono, and both rely on Microsoft-specific underpinnings. That said, you should still be able to use .asmx web services with Mono and get into any DBMS you wish with a telnet connection. *Again, this completely eliminates the DBMS-specific SOAP/XML issues, and you get a nice platform-independent comms component out of the deal. The differences between mv.NET and a homegrown .NET inteface via telnet are numerous, but here are just a couple: - mv.NET has session pooling and auto increase/decrease of sessions as required - mv.NET actually has 4 deep libraries to choose from rather than just simple classes to mimic MVBASIC - mv.NET has a code generator to build business objects, similar to NHibernate or CSLA - mv.NET is fully supported with an aggressive roadmap for ongoing enhancements So anyway, have a look around my blog for articles like "Why .NET", see the code samples on our site, and feel free to contact me for a free trial. HTH Tony Gravagno Nebula Research and Development TG@ remove.pleaseNebula-RnD.com Nebula R&D sells mv.NET and other Pick/MultiValue products worldwide, and provides related development services remove.pleaseNebula-RnD.com/blog Visit PickWiki.com! Contribute!http://Twitter.com/TonyGravagno |
#4
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |