Wrox Programmer Forums
Welcome to the p2p.wrox.com Forums.

You are currently viewing the WinForms/Console Application Design section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old July 24th, 2008, 07:54 AM
Registered User
Join Date: Jul 2008
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default Big Desktop Database Application


I am designing a .NET database application that uses 3 tier architecture. Starting initially, this application will be desktop application but I will convert it into a website later but design that I am planning should support both version.

Development Environment : VS2008,C#
Currently Database supported are MS SQL Server 2005 and MYSQL 5 and design for database support is extensible.

This application contains several high level modules (HLM) that can either share the data from the database of other high modules and some are totally independent modules.

Like say finance and project automation are not dependent on each other but finance and investments are. These are some examples of the modules that will be used in this the application.

For website version of this app,
Main Website will <mainapplication>.com and
High level module (HLM) will be having subdomain names like
<HLM1>.<mainapplication>.com ,
<HLM2>.<mainapplication>.com and so on.

Database Name : <mainapplication>

Now for desktop version should I create different <HLM> EXE application and linked them to the main application and share the same database with all the apps?

I like the design of MS Money application for desktop application. However, this is only a finance application and it is also that big. Can that design help me for this scenario or are there any references of big desktop application that is extensible and contains support for database ?

Currently I have research enough on desktop application for
1. Inter process communication can be using named pipes, since it is on same machine.
2. Single Sign on in main application will allow access to other HLM exe application.
3. Only Main application will call the other HLM application. Running HLM Exe alone will give a error .
4. New HLM application will have a module code and store in the database and loaded in the main application once logged in. Using module code, the HLM exe will be loaded.
5. Main application will have framework to support dynamic linking of HLM and have base libraries that will be implemented and use by HLM exe application.
6. Each HLM exe will have its separate BO and DAO layers.
7. If HLM B depends on HLM A then HLM B will reference HLM A BO layer for calling functionalities that are required.
8. There will be only 1 instance of the any application running at anytime time.

I am not sure of the following
1. Transaction handling between multiple processes.
2. If there are anything else that I need to take care of

Can anyone please help me decide and answer the queries so that I can move on with the development of the application. This will be big application should the design and architecture should be finalize first.

Similar Threads
Thread Thread Starter Forum Replies Last Post
security for Desktop application mattphung Pro VB.NET 2002/2003 5 May 30th, 2008 12:32 PM
DotNet Desktop Application with Oracle aliirfan84 ADO.NET 3 January 17th, 2007 01:38 AM
how to use css in C#(desktop application) ahmad_diab85 C# 1 December 28th, 2006 12:56 PM
send email desktop application vipinpaliwal1980 VB.NET 2002/2003 Basics 0 April 19th, 2006 10:54 PM
sending email from desktop application sandeepdubey1980 VS.NET 2002/2003 3 September 2nd, 2005 02:49 PM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.