Separate component classes from ASP.NET project?

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Dan Trahan via .NET 247 (anonymous_at_dotnet247.com)
Date: 12/23/04

  • Next message: Mark Nugent via .NET 247: "Windows Service cannot instantiate object of external class???" 
    Date: Wed, 22 Dec 2004 16:04:14 -0800

    I'm fairly new to developing applications in .NET and I'm investigating a good design pattern to upgrade an existing ASP/COM+ application into .NET.

    There is a fairly large set of COM+ dll's for the middle-tier in the ASP/COM+ app. My question relates to the location of these components when they are upgraded to .NET component classes.

    1) Is there any benefit to compiling the component classes separate from the web site (ASP.NET) vs. compiling all the component classes with the ASP.NET pages into one DLL?

    2) Does either method affect other applications (these could be legacy ASP/COM+ apps or other ASP.NET websites) from accessing these component classes? For example, some legacy applications might still be using the COM+ interface to access these components.

    Any information on the above would be greatly appreciated.

    Best Regards,
    Dan Trahan

    -----------------------
    Posted by a user from .NET 247 (http://www.dotnet247.com/)

    <Id>ppQMEXYSiUC2f942gCtwCw==</Id>

  • Next message: Mark Nugent via .NET 247: "Windows Service cannot instantiate object of external class???"

    Relevant Pages

    • Separate component classes from ASP.NET project?
      ... I'm fairly new to developing applications in .NET and I'm investigating a good design pattern to upgrade an existing ASP/COM+ application into .NET. ... Is there any benefit to compiling the component classes separate from the web site vs. compiling all the component classes with the ASP.NET pages into one DLL? ...
      (microsoft.public.dotnet.framework.component_services)
    • Separate component classes from ASP.NET project?
      ... I'm fairly new to developing applications in .NET and I'm investigating a good design pattern to upgrade an existing ASP/COM+ application into .NET. ... Is there any benefit to compiling the component classes separate from the web site vs. compiling all the component classes with the ASP.NET pages into one DLL? ...
      (microsoft.public.dotnet.framework.component_services)
    • Separate component classes from ASP.NET project?
      ... I'm fairly new to developing applications in .NET and I'm investigating a good design pattern to upgrade an existing ASP/COM+ application into .NET. ... Is there any benefit to compiling the component classes separate from the web site vs. compiling all the component classes with the ASP.NET pages into one DLL? ...
      (microsoft.public.dotnet.framework.component_services)
    • Separate component classes from ASP.NET project?
      ... I'm fairly new to developing applications in .NET and I'm investigating a good design pattern to upgrade an existing ASP/COM+ application into .NET. ... Is there any benefit to compiling the component classes separate from the web site vs. compiling all the component classes with the ASP.NET pages into one DLL? ...
      (microsoft.public.dotnet.framework.component_services)
    • Re: Installing ALSA ... (continued.) ["Against Techno-Fetishism !"]
      ... You have given me the encouragement and incentive I needed to upgrade ... I'll have to read up on static compiling but I'm glad to hear that ... Adam Bogacki, ... > statically and it just worked first time. ...
      (Debian-User)