ASP3/VB6 to ASP.NET/VB.NET

[Carl Howarth]

Hi,

At my organisation we have various web based systems in place using ASP 3.0
for the front end but with VB6 ActiveX DLLs (installed within component
services) for the business logic.

I am aware that with VB.NET I can still create a dll and access it within
the ASP.NET, but that it is not possible to install this dll within
component services.

What is the best route so that we may share code throughout various
web-based and non-web-based applications - should I continue to create DLLs
in VB.NET and use them within the ASP.NET, and if so does it not matter that
the component is not registered within component services?

Any advice would be greatly appreciated.

Kind regards,

Carl Howarth
[email]carl.howarth@m-s-solutions.co.uk[/email]

[Steve C. Orr, MCSD]

Component Services shouldn't be an issue.
..NET can interact with Component Services just fine through the
EnterpriseServices namespace.
Here's more info:
[url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemEnterpriseServices.asp[/url]
[url]http://www.microsoft.com/traincert/syllabi/2557AFinal.asp[/url]
[url]http://www.dotnet247.com/247reference/System/EnterpriseServices/System.EnterpriseServices.aspx[/url]
[url]http://webref.info/default.asp?ID=9876[/url]

--
I hope this helps,
Steve C. Orr, MCSD
[url]http://Steve.Orr.net[/url]


"Carl Howarth" <carl.howarth@m-s-solutions.co.uk> wrote in message
news:%23zXxjbWRDHA.3880@tk2msftngp13.phx.gbl...

> Hi,
>
> At my organisation we have various web based systems in place using ASP

3.0

> for the front end but with VB6 ActiveX DLLs (installed within component
> services) for the business logic.
>
> I am aware that with VB.NET I can still create a dll and access it within
> the ASP.NET, but that it is not possible to install this dll within
> component services.
>
> What is the best route so that we may share code throughout various
> web-based and non-web-based applications - should I continue to create

DLLs

> in VB.NET and use them within the ASP.NET, and if so does it not matter

that

> the component is not registered within component services?
>
> Any advice would be greatly appreciated.
>
> Kind regards,
>
> Carl Howarth
> [email]carl.howarth@m-s-solutions.co.uk[/email]
>
>