Thursday, April 18, 2002

Developing a Pocket-PC application that calls a WebService This article demonstrates how to call .NET web service from Pocket PC application. The Pocket PC application will pass data using Pocket SOAP (Simple Object Access Protocol) to the web service (therefore IIS with .NET framework is required on the server) and return result back to the Pocket PC application. Article. Apr 18, 2002. An article using Simon's PocketSOAP 10:34:45 PM

I just got home from a meeting of the New Hampshire .NET User's Group tonight where my good friend Jim Murphy gave an excellent presentation on ".NET Resource Management - GC and Dispose" and I find an Amazon package containing Ingo's book Advanced .NET Remoting. Finally!! 10:07:44 PM

Way Excellent! Terrific Threesome create OS .NET Remoting Site Regular readers of this blog will notice that I don't generally repost other people's blog entries without commentary. However, since I'm involved in this effort, this is the exception to the rule: Ingo posted this as "Revealing the sources and calling for action!": Peter Drayton, Simon Fell and I are proud to announce a set of open source .NET Remoting projects. We have planned this for some time now and after Simon created the CVS repository last week, I finally got the time to create a web site about them. http://www.dotnetremoting.cc/projects We have currently implemented a JabberChannel which allows .NET Remoting messages to be transferred via the Jabber protocol and an SMTP/POP3-channel which uses standard internet email to transport the requests and responses. Both channels come with full source code, sample clients and servers and are covered by a very liberal open source license. One of the reason for kicking this off right now is that we want to provide a collaborative environment for remoting-related developments. At the current time we are about to implement the following (parts of them will be available in the CVS in a week or two) * An XML-RPC Formatter for .NET Remoting * A bidirectional TCPChannel which avoids the problems with callbacks, events and sponsors which are used from clients behind NATs or firewalls. * A caching channelsink (based on this idea) * A framework for the development of feature complete custom channels * An MSN Messenger channel Further ideas which we think about are * A document/literal encoding SOAP formatter * A DIME/TCPChannel * and finally, an implementation of the GXA-specs (WS-Routing, WS-Security) This post is also a call for action! If you already implemented channels or sinks or have some great ideas about doing so, please don't hesitate to contact me privately or - even better - post them to the project discussion forum. Also please check the licensing information before submitting any source code to this project as we definitely don't want to infringe of any existing copyrights. Thanks for your support. I'd really like to hear your opinions on this. Please blog, email or post at them the forum! Happy coding! [Peter Drayton's Radio Weblog] 9:54:28 PM

The .NET Compact Framework beta 1 is about to become available. This will finally bring C# and the rest of the .NET goodies to the Pocket PC crowd. If you are interested in signing up for the beta, check out the Microsoft GotDotNet website for more information. 6:40:08 AM

The SQL Server Notification Services beta is taking applicants. Notification Services is described as "A platform for developing and deploying highly scalable rich push applications" - basically it's a sophisticated publish/subscribe system that can deliver alerts via SMTP email, HTTP Posts, files in drop directories, and (more interestingly) MSN IM .NET Alerts. [Peter Drayton's Radio Weblog] 6:31:52 AM

© Copyright 2002 Sam Gentile.