Using ASP.Net and VB/COM
It seems to me that the most compelling reason to move quickly to VS.Net
is to use ASP.Net to create web apps, instead of ASP. The return on investment
would be immediate, considering how much more quickly web apps could be created.
In the meantime I could continue to create my COM components with VB6, ADO
etc, and use the COM interop libraries to call them from ASP.Net. Once I
am comftable with ASP.Net I can begin developing my components in either
C# or VB.Net.
Of course I would have to use either C# or VB.Net to in ASP, but the amount
of ASP code I write is minimal anyway.
Does this sound like a sensible strategy, or should I jump in the deep end
and sink or swim?
Re: Using ASP.Net and VB/COM
Sounds very sensible. The unfortunate side of gettig new tools and
technologies is the short term loss pf productivity until you learn them.
However once you get to the top of the curve with .NET you will find the
overall productivity to be much greater then what you are seeing now.
BTW be careful with th COM interop. It does work well, but there is some
overhead with doing it. Keep the calls between COM and managed code
(ASP.NET) as minimal as possible.
> In the meantime I could continue to create my COM components with VB6, ADO
> etc, and use the COM interop libraries to call them from ASP.Net. Once I
> am comftable with ASP.Net I can begin developing my components in either
> C# or VB.Net.
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL