new project - remoting, webservices or WCF?

[=?Utf-8?B?S2FpIEZyYW5zc29u?=]

We're starting a new project with a distributed winform client that
communicates with a central server, primarily all on the same LAN. Large
amounts of data may be sent to and from the client.

My first thought was to use WCF but I was sad to learn that Framework 3 is
not supported on Win 2k workstations, so that is unfortunately not an option
:-(

I like the better speed of _remoting_ over _webservices_, especially since
we are talking about an intranet application.

What technology would you recommend for a new project like this, starting
today?

I would like to be able to switch to WCF in the future when we no longer
need to run the client on Win2k workstation. Would it perhaps be best to have
the server expose separate kinds of "facades" so that a client can connect
using either Remoting, asmx webservices or WCF (This would also require the
client to be able to switch between these ways fo communication)?

Advices on technology, and recommendations of good examples on the web, are
greatly appreciated.

Best Regards
/KF

[=?Utf-8?B?S2FpIEZyYW5zc29u?=]

I should perhaps add that the server part of the application will run on a
Win 2003 server.
"Kai Fransson" wrote:

We're starting a new project with a distributed winform client that
communicates with a central server, primarily all on the same LAN. Large
amounts of data may be sent to and from the client.

My first thought was to use WCF but I was sad to learn that Framework 3 is
not supported on Win 2k workstations, so that is unfortunately not an option
:-(

I like the better speed of _remoting_ over _webservices_, especially since
we are talking about an intranet application.

What technology would you recommend for a new project like this, starting
today?

I would like to be able to switch to WCF in the future when we no longer
need to run the client on Win2k workstation. Would it perhaps be best to have
the server expose separate kinds of "facades" so that a client can connect
using either Remoting, asmx webservices or WCF (This would also require the
client to be able to switch between these ways fo communication)?

Advices on technology, and recommendations of good examples on the web, are
greatly appreciated.

Best Regards
/KF

[Scott M.]

Since you can't use WCF and you need to make this application today, I would
say that your choice of remoting vs. web services would then come down to
the need for a proprietary/fast solution or the need for an
non-proprietary/slightly slower solution.

Today, it seems that you don't need to worry about a non-proprietary
solution, so remoting would be fine, but what about the future? Will WCF
save the day BEFORE you need to worry about scaling outside of the intranet?
This is really all you need to think about. Converting a remoting app. to
WCF should be no more troublesome that converting a web service app., so WCF
wouldn't really factor into the decision making process.

-Scott
"Kai Fransson" <Ka*********@discussions.microsoft.comwrote in message
news:F4**********************************@microsof t.com...

>I should perhaps add that the server part of the application will run on a
Win 2003 server.
"Kai Fransson" wrote:

>We're starting a new project with a distributed winform client that
communicates with a central server, primarily all on the same LAN. Large
amounts of data may be sent to and from the client.

My first thought was to use WCF but I was sad to learn that Framework 3
is
not supported on Win 2k workstations, so that is unfortunately not an
option
:-(

I like the better speed of _remoting_ over _webservices_, especially
since
we are talking about an intranet application.

What technology would you recommend for a new project like this, starting
today?

I would like to be able to switch to WCF in the future when we no longer
need to run the client on Win2k workstation. Would it perhaps be best to
have
the server expose separate kinds of "facades" so that a client can
connect
using either Remoting, asmx webservices or WCF (This would also require
the
client to be able to switch between these ways fo communication)?

Advices on technology, and recommendations of good examples on the web,
are
greatly appreciated.

Best Regards
/KF

[=?Utf-8?B?S2FpIEZyYW5zc29u?=]

I read somewhere that you can expose more than one endpoint from your WCF
service, so that clients running win2000 can also communicate with your WCF
service. Is this worthwhile, or should I just build a classic remoting app
and then convert it to WCF when the time comes?

Also, any good reading or samples would be appreciated.

/Kai

"Scott M." wrote:

Since you can't use WCF and you need to make this application today, I would
say that your choice of remoting vs. web services would then come down to
the need for a proprietary/fast solution or the need for an
non-proprietary/slightly slower solution.

Today, it seems that you don't need to worry about a non-proprietary
solution, so remoting would be fine, but what about the future? Will WCF
save the day BEFORE you need to worry about scaling outside of the intranet?
This is really all you need to think about. Converting a remoting app. to
WCF should be no more troublesome that converting a web service app., so WCF
wouldn't really factor into the decision making process.

-Scott
"Kai Fransson" <Ka*********@discussions.microsoft.comwrote in message
news:F4**********************************@microsof t.com...

I should perhaps add that the server part of the application will run on a
Win 2003 server.
"Kai Fransson" wrote:

We're starting a new project with a distributed winform client that
communicates with a central server, primarily all on the same LAN. Large
amounts of data may be sent to and from the client.

My first thought was to use WCF but I was sad to learn that Framework 3
is
not supported on Win 2k workstations, so that is unfortunately not an
option
:-(

I like the better speed of _remoting_ over _webservices_, especially
since
we are talking about an intranet application.

What technology would you recommend for a new project like this, starting
today?

I would like to be able to switch to WCF in the future when we no longer
need to run the client on Win2k workstation. Would it perhaps be best to
have
the server expose separate kinds of "facades" so that a client can
connect
using either Remoting, asmx webservices or WCF (This would also require
the
client to be able to switch between these ways fo communication)?

Advices on technology, and recommendations of good examples on the web,
are
greatly appreciated.

Best Regards
/KF

[Spam Catcher]

=?Utf-8?B?S2FpIEZyYW5zc29u?= <Ka*********@discussions.microsoft.com>
wrote in news:4C**********************************@microsof t.com:

I read somewhere that you can expose more than one endpoint from your
WCF service, so that clients running win2000 can also communicate with
your WCF service. Is this worthwhile, or should I just build a classic
remoting app and then convert it to WCF when the time comes?

Yup true - you can still use WCF - but just use the web service channel.

[=?Utf-8?B?S2FpIEZyYW5zc29u?=]

Traditionally we've used Com+ Enterprise Services for scalability and
transaction handling. Do you have any recommendations for achieving this
using WCF?

Most examples I find host their WCF services in a console app, which cannot
be best practice for creating a facade for my server application. Is a
windows service a good facade for my server application? Any advice is
greatly appreciated.

/Kai

"Spam Catcher" wrote:

=?Utf-8?B?S2FpIEZyYW5zc29u?= <Ka*********@discussions.microsoft.com>
wrote in news:4C**********************************@microsof t.com:

I read somewhere that you can expose more than one endpoint from your
WCF service, so that clients running win2000 can also communicate with
your WCF service. Is this worthwhile, or should I just build a classic
remoting app and then convert it to WCF when the time comes?

Yup true - you can still use WCF - but just use the web service channel.

[Spam Catcher]

=?Utf-8?B?S2FpIEZyYW5zc29u?= <Ka*********@discussions.microsoft.com>
wrote in news:2C**********************************@microsof t.com:

Traditionally we've used Com+ Enterprise Services for scalability and
transaction handling. Do you have any recommendations for achieving
this using WCF?

Here you go:

http://msdn2.microsoft.com/en-us/library/bb735856.aspx

FYI, .NET 2.0 and WCF has transactional support - so perhaps it might be
good enough without resorting to COM+.

Most examples I find host their WCF services in a console app, which
cannot be best practice for creating a facade for my server
application. Is a windows service a good facade for my server
application? Any advice is greatly appreciated.

Absolutely. Console App vs. Windows Form vs. Services is all schematics.
The underlying syntax is identical across the board... and the way WCF
works is the same.

[=?Utf-8?B?UkFKQQ==?=]

Hi Fransson,

My project also same like this. Let me know whether i can use the WCF or
Remorting? Can you guide me abt this?

Regards,
RAJA

"Kai Fransson" wrote:

We're starting a new project with a distributed winform client that
communicates with a central server, primarily all on the same LAN. Large
amounts of data may be sent to and from the client.

My first thought was to use WCF but I was sad to learn that Framework 3 is
not supported on Win 2k workstations, so that is unfortunately not an option
:-(

I like the better speed of _remoting_ over _webservices_, especially since
we are talking about an intranet application.

What technology would you recommend for a new project like this, starting
today?

I would like to be able to switch to WCF in the future when we no longer
need to run the client on Win2k workstation. Would it perhaps be best to have
the server expose separate kinds of "facades" so that a client can connect
using either Remoting, asmx webservices or WCF (This would also require the
client to be able to switch between these ways fo communication)?

Advices on technology, and recommendations of good examples on the web, are
greatly appreciated.

Best Regards
/KF

[Scott M.]

I think if you read the other posts in this thread, you'll have your answer.

"RAJA" <RA**@discussions.microsoft.comwrote in message
news:C6**********************************@microsof t.com...

Hi Fransson,

My project also same like this. Let me know whether i can use the WCF or
Remorting? Can you guide me abt this?

Regards,
RAJA

"Kai Fransson" wrote:

>We're starting a new project with a distributed winform client that
communicates with a central server, primarily all on the same LAN. Large
amounts of data may be sent to and from the client.

My first thought was to use WCF but I was sad to learn that Framework 3
is
not supported on Win 2k workstations, so that is unfortunately not an
option
:-(

I like the better speed of _remoting_ over _webservices_, especially
since
we are talking about an intranet application.

What technology would you recommend for a new project like this, starting
today?

I would like to be able to switch to WCF in the future when we no longer
need to run the client on Win2k workstation. Would it perhaps be best to
have
the server expose separate kinds of "facades" so that a client can
connect
using either Remoting, asmx webservices or WCF (This would also require
the
client to be able to switch between these ways fo communication)?

Advices on technology, and recommendations of good examples on the web,
are
greatly appreciated.

Best Regards
/KF

[=?Utf-8?B?UkFKQQ==?=]

Thanks. I'll check it.

"Scott M." wrote:

I think if you read the other posts in this thread, you'll have your answer.

"RAJA" <RA**@discussions.microsoft.comwrote in message
news:C6**********************************@microsof t.com...

Hi Fransson,

My project also same like this. Let me know whether i can use the WCF or
Remorting? Can you guide me abt this?

Regards,
RAJA

"Kai Fransson" wrote:

We're starting a new project with a distributed winform client that
communicates with a central server, primarily all on the same LAN. Large
amounts of data may be sent to and from the client.

My first thought was to use WCF but I was sad to learn that Framework 3
is
not supported on Win 2k workstations, so that is unfortunately not an
option
:-(

I like the better speed of _remoting_ over _webservices_, especially
since
we are talking about an intranet application.

What technology would you recommend for a new project like this, starting
today?

I would like to be able to switch to WCF in the future when we no longer
need to run the client on Win2k workstation. Would it perhaps be best to
have
the server expose separate kinds of "facades" so that a client can
connect
using either Remoting, asmx webservices or WCF (This would also require
the
client to be able to switch between these ways fo communication)?

Advices on technology, and recommendations of good examples on the web,
are
greatly appreciated.

Best Regards
/KF