I am assessing whether a .net intranet application system is of acceptable, reasonable quality. My criteria so far for this is on several fronts: - Architecture (e.g., is the architecture n-tier?) - Is the code easy to maintain? - Has the code been written with reuse in mind, or refactored? - Are there...
Posted to
Free For All
(Forum)
by
dbrook007
on
01-04-2008, 12:00 AM
Filed under: design pattern, entity, web service, Class Design, VB Class, Generics, OOP, .NET, caching, data serialization, vb.net, Reflection, VB, Basic Architecture Design, Data modeling, ASP.NET Architecture, VB Classes, architecture, solution project, datagrid, Patterns & Practices, N-Tier, database object, performance, Website Problem, authentication, Exception Handling, data access object relational mapping, DAL exceptions, business logic layer, partial classes, Events, database, assemblies, sql server, Best Practices, http, dataobjects, 3-tier programming, datalogic layer, Globalization, 3-Tier Architecture, ntier, 3tier, GridView, Asp.Net 2.0, persist changes, assembly, xml, css, UI Process Components, data access layer, System Design, Exception Handling Application Block, Exception Handling Application Block Tutorial, CustomErrorPage, asp.net tuning, optimization, application state management, IIS, UI Framework, Consistency in UI, approach, UI Architecture, Technical Specification, Asp.Net 2.0 : java script, bug, ADO.NET, system analysis", "system Design", Data Concurrency, Report Viewer, methods, ASP.NET 2.0 NET SQL Server 2005 database connection error, arcitecture, Web Forms, business model, concurrentcy