wcf - "Best" way to communicate between .NET 1.1 and .NET 3.5 -


by best mean:

  • cheapest development cost (1.1 project unlikely live > 6 months)
  • easiest migration wcf or similar

by communicate between mean:

  • remote communication between computers
  • most no firewall restrictions

with .net 1.1 options appear be: sockets, remoting, , various flavours of web service.

the option of using binary serialized datatables on sockets has been proposed solution wary of this.

update: "server" in case windows embedded standard .net 1.1. @ stage unable add new components image such iis, asp, or msmq etc. take consideration

since migrating wcf, may want consider building wcf service immediately, using basichttpbinding, supports old asmx style web-services, i.e. ws-basicprofile 1.1. able consume service .net 1.1 application.

you can consider using msmqintegrationbinding in wcf, .net 1.1 application post/receive messages msmq.

you may want check out following related articles:


Comments

Popular posts from this blog

ruby - When to use an ORM (Sequel, Datamapper, AR, etc.) vs. pure SQL for querying -

php - PHPDoc: @return void necessary? -

c++ - Convert big endian to little endian when reading from a binary file -