We have quite some time developing 3-tier systems in VB6 and are starting to
develop a new version of our corporate system. Right now we're struggling
with one big issue: which way to go?
After reading hundreds of docs about servicedcompone nts and .net remoting, I
have a crucial question that I would like to ask you.
What are the recommended strategies to develop a transactional corporate
system, like we used to do in VB old days (if possible, could you also point
some links about these architectures recommended)?
As a matter of fact, we've already started to develop a presentation only
prototype, of a few screens and classes in VB.Net, assuming that we were
going to use COM+ with Windows 2003 server. Before, I had read a lot about
serviced components and also that Microsoft would keep COM+ because it's a
good tool etc... But before we go on, I'd like to know other opinions. So,
I'd like to count your help to enlight me over these issues.
Thanks in advance and forgive my poor "brazilian english",
Arnaldo Fuziy.
develop a new version of our corporate system. Right now we're struggling
with one big issue: which way to go?
After reading hundreds of docs about servicedcompone nts and .net remoting, I
have a crucial question that I would like to ask you.
What are the recommended strategies to develop a transactional corporate
system, like we used to do in VB old days (if possible, could you also point
some links about these architectures recommended)?
As a matter of fact, we've already started to develop a presentation only
prototype, of a few screens and classes in VB.Net, assuming that we were
going to use COM+ with Windows 2003 server. Before, I had read a lot about
serviced components and also that Microsoft would keep COM+ because it's a
good tool etc... But before we go on, I'd like to know other opinions. So,
I'd like to count your help to enlight me over these issues.
Thanks in advance and forgive my poor "brazilian english",
Arnaldo Fuziy.