Component Services shouldn't be an issue.
..NET can interact with Component Services just fine through the
Here's more info:
I hope this helps,
Steve C. Orr, MCSD
"Carl Howarth" <carl.howarthm-s-solutions.co.uk> wrote in message
> At my organisation we have various web based systems in place using ASPDLLs> 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 createthat> in VB.NET and use them within the ASP.NET, and if so does it not matter> the component is not registered within component services?
> Any advice would be greatly appreciated.
> Kind regards,
> Carl Howarth