solution design - I'm stuck

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



I have a few different choices when it comes to solution design:

1. Put all UI elements in a single dll and all other data, processing and
logic goes in all other dlls specific to a particular feature (like News,
Events or data access), or
2. Put all elements like business logic and UI in a dll specific to a
feature (like News or Events) and put the data access by itself.


This is keeping in mind that whichever one I choose, the presentation layer
(the actual pages themselves) will be kept in the website which will be
seperated from the UI, business, foundation services and data access
modules.


.



Relevant Pages

  • Re: Does anyone know why this SQL doesnt work on different ODBC versions using ADO
    ... msadcer.dll |Microsoft Data Access - OLE DB Cursor Engine ... msader15.dll|Microsoft Data Access - ActiveX Data Objects ... MSVCIRT.dll |Windows NT IOStreams DLL ...
    (borland.public.delphi.database.ado)
  • Re: Prevent DLL usage
    ... StackTrace st = new StackTrace; ... The Business Logic DLL references the Data Access DLL. ... No other .net assemblies may use the Data Access DLL. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Prevent DLL usage
    ... The Business Logic DLL references the Data Access DLL. ... No other .net assemblies may use the Data Access DLL. ...
    (microsoft.public.dotnet.languages.csharp)
  • Prevent DLL usage
    ... The Business Logic DLL references the Data Access DLL. ... No other .net assemblies may use the Data Access DLL. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Strange situation ---how is this happening?
    ... code behind page and the updated dll to the live server. ... You modified existing code to provide this new feature. ... branch your source control tree to allow bug fixes in one body of code ...
    (microsoft.public.dotnet.framework.aspnet)