Using ASP.Net with VB/COM

[Richardb]

Hi,

It seems to me that the most compelling reason to move quickly to .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?

cheers, Richard,

[Ian Drake]

<MyOpinion>
You are correct that ASP.NET will have imidiate and substantial performance
gains over ASP 2 or 3 and that ASP.NET pages are easier to develop than traditional
ASP. However, it is only easier to program with ASP.NET if you know how....and
if you know how then realisticly you should know how to develop your components
in .NET. I would only recommend using the COM interop for existing COM components.
If I were to list the advantages and disadvantages of creating COM components
for ASP.NET, I can't think of anything on the advantages side (assuming you
are a capable ASP.NET programer, making you a capable .NET programmer).
ASP.NET is much more powerful now, but that comes at a price. It is no longer
a toy, and can't just be played with. It is as difficult to develop an ASP.NET
page as it is to develop business or data compoents in .NET.
</MyOpinion>

Good Luck
Ian Drake

[Richardb]

"Ian Drake" <ian@dotetnut.com> wrote:
>
><MyOpinion>
>You are correct that ASP.NET will have imidiate and substantial performance
>gains over ASP 2 or 3 and that ASP.NET pages are easier to develop than
traditional
>ASP. However, it is only easier to program with ASP.NET if you know how....and
>if you know how then realisticly you should know how to develop your components
>in .NET. I would only recommend using the COM interop for existing COM
components.
> If I were to list the advantages and disadvantages of creating COM components
>for ASP.NET, I can't think of anything on the advantages side (assuming
you
>are a capable ASP.NET programer, making you a capable .NET programmer).

>ASP.NET is much more powerful now, but that comes at a price. It is no
longer
>a toy, and can't just be played with. It is as difficult to develop an
ASP.NET
>page as it is to develop business or data compoents in .NET.
></MyOpinion>
>
>Good Luck
>Ian Drake

Hi Ian,

Thanks for the reply.

My web skills are comparitively weak compared with my VB/COM skills, which
is why I would like to be able to concentrate on the ASP.Net for a while.

I recently created a Prototype web application using VB/COM+ components,
ASP and client-side Javascript. With a solid VB/Com background, I could create
the components quickly and easily, but the asp amd html pages took longer,
especially the more complex pages using client side javascript.

HTML may be easy to understand, but it can be very messy when combined with
Javascipt. I found that the Windows DNA model did not place enough importance
on client side script, simply labelling it the "thin client" with no further
explanation. I have found it to be very useful in performing client side
validation etc without having to post data to the server.

Anyway, the people in this news group would already know this.

cheers, richard.

[Greg Rothlander]

It is my understanding that when you create the C# and VB.Net code, you will
actually be creating COM object much like you currently do. I believe that
you could create the COM object in any language and use them in your ASP.Net
applications in a similar manner....this is what I've been doing The .Net
IDE lets you do this a bit more easy but it's basically the same thing.
In .Net you create a project that connects the COM objects with the ASP.Net
code but they are actually seperate. You can hard code the ADO.Net and VBScript
in the ASP.Net page, much like 90%+ of the existing ASP code, but I would
not recommend it.

"Richardb" <Rbuckingham@loyalty-magic.com> wrote:
>
>Hi,
>
>It seems to me that the most compelling reason to move quickly to .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?
>
>cheers, Richard,