dilettante
MIS
Here's a start at a thread asking "what the heck does Dot-Net do for me, the developer" and "what's cool/useful about VB.Net for the VBer?"
Here are some initial stabs at it. I would welcome additions and corrections. And when we venture into opinion, a bit of discussion.
WHAT'S .NET GET ME?
* End of .dll-hell (?)
* Return to "rich-client" application development through the death of the deployment dragon (?)
* Highly granular distributed computing using web services (?)
* Loosely-coupled, potentially multiplatform, firewall-penetrating RPC-like DCOM replacement/supplement [SOAP and such] (?)
* Support for multiple programming languages, rather than Sun's Java-centric view of computing (?)
WHAT'S VB.NET GET ME?
* Use VB to create server-side objects with less threading restrictions (????)
* Clean(er) interoperation with components written other CLR-based programming languages (?)
RANDOM OPINION
I always figured part of the motivation for SOAP was to use TCP port 80 and HTTP because of the constant war between distributed developers and firewall keepers. I know firewalls make DCOM and database access a nightmare for me, especially every time there's an attempt to "clean up" the rules or upgrade firewall software.
Here are some initial stabs at it. I would welcome additions and corrections. And when we venture into opinion, a bit of discussion.
WHAT'S .NET GET ME?
* End of .dll-hell (?)
* Return to "rich-client" application development through the death of the deployment dragon (?)
* Highly granular distributed computing using web services (?)
* Loosely-coupled, potentially multiplatform, firewall-penetrating RPC-like DCOM replacement/supplement [SOAP and such] (?)
* Support for multiple programming languages, rather than Sun's Java-centric view of computing (?)
WHAT'S VB.NET GET ME?
* Use VB to create server-side objects with less threading restrictions (????)
* Clean(er) interoperation with components written other CLR-based programming languages (?)
RANDOM OPINION
I always figured part of the motivation for SOAP was to use TCP port 80 and HTTP because of the constant war between distributed developers and firewall keepers. I know firewalls make DCOM and database access a nightmare for me, especially every time there's an attempt to "clean up" the rules or upgrade firewall software.