If you are at the beginning of the road for distributed architecture as of
today.
Then WCF is your starting point. It is the fruition of many previous DotNet
technologies like Remoting and MSMQ.
If you are going to be working in a "DotNet to DotNet" world , where all of
your clients are DotNet enabled, then look here:
http://sholliday.spaces.live.com/blog/cns!A68482B9628A842A!158.entry
If you're going to support non dot net clients (java, asp, other), then WCF
is still the answer. But you will generate proxies for the client, instead
of my interface method.
...................
I also have a Remoting entry at my blog you might read over as well. Its
about "keeping your secret code safe". However, that is an old article, and
you want to learn from Remoting, but WCF is the way to go.
...............
You might also check out some videos on channel9 from Greg Leake.....about
the stocktrader sample application.
http://www.google.com/search?hl=en&q...el9+greg+leake
There are 2 videos to watch. They're roughly 2 hours (in total).
"z71mdridin" <z7********@gmail.comwrote in message
news:24**********************************@k39g2000 hsf.googlegroups.com...
>I currently have a classic asp/COM+ architecture setup as following:
Server A- hosts all the classic asp front end pages
Server B- host all the business layer dlls. They are currently
registered through COM+
Server C- contains database
We are migrating to .NET and I would like to keep the same distributed
architecture, but it appears that asp.net applications copy all the
business layer dlls into their bin directory. I know that distributed
computing must be possible in .NET but I am overlooking something.
Can anyone give me any suggestions?
Any help you provide would be greatly appreciated! Thanks.
