CodeBetter.Com
CodeBetter.Com
RSS 2.0 via Feedburner
           Do you Twitter? Follow us @CodeBetter

Grant Killian's Blog

No, this has nothing to do with beer -- but maybe it should?

ASMX=confident; Remoting=lessConfident;

Don Box confirms that we should go forth with confidence and use Web Services and ASMX; Whidbey, Indigo, and the future frameworks build on this infrastructure -- they don't discard it

I'm not so sure about Remoting, however.  Various sources indicate that Remoting, as we know it, will be different with Indigo and Longhorn and require “non-trivial“ programming changes.  Any talk like that is enough to scare new adopters from a technology . . . is there anything definitive yet?

Happy .Netting!



Comments

Grant said:

Thanks Piyush, that's a good answer!

To quote Turner's post: "We recommend minimizing your use of .NET Remoting to these niche areas, and suggest that you utilize Enterprise Services for the development of components inside your services, and ASMX/WSE for exposing your services at your boundaries."

I'd be certain Remoting is the right choice for your situation before jumping hog wild into it!
# April 23, 2004 3:29 AM

Don Box said:

See http://www.gotdotnet.com/team/dbox/default.aspx?key=2004-04-26T03:14:52Z for a direct (if long) response from yours truly.

DB
# April 26, 2004 4:15 AM

Jiho Han said:

Excuse my ignorance but what is TP/SBS?

Thanks
# April 27, 2004 9:45 AM

Don Box said:

Transparent Proxy/Stack Builder Sink
# April 27, 2004 12:35 PM

Leave a Comment

(required)  
(optional)
(required)  

Enter the numbers above:
Add
Check out Devlicio.us!