|
Hi folks, i'm relatively new to this area of things although i have been using C# for many years. I have been trying to find a starting point for organizing my code for medium sized projects. What i am after is a relatively detailed example of how a software application solution would be organized in Visual Studio. For example if i worked for company CMP and had an application i wished to create named AppX, no doubt i would start with a solution named: CMP.AppX .. and then begin adding projects. I am aware that every situation would be different and would require different projects and namespaces, but i would like an example of how you guys would go about doing it and some reasons for your choices. eg:
CMP.AppX
CMP.AppX.Data
CMP.AppX.UI
CMP.AppX.UI.Desktop
CMP.AppX.UI.Web
CMP.AppX.Webservices
CMP.AppX.UnitTests
CMP.AppX.Reporting
...and how this would be achieved - what was a project and what was subdir in the project folder etc. Thanks in advance.
|
|
|
|
|
We organize our projects normally in this way:
1)
One solution for all projects we are currently developing. Developing with several solutions at once is very cumbersome.
2)
However, if there are components that can be extracted in some sort of library or framework then do it (only feasable for components that can be developed independently for the most part, because of 1)
3)
If our system is built up from different "sub-systems" (sometimes there is a relationship with tiers, but it's possible to have either several sub-systems per tier or viceversa) then we arrange them within solution folders (note that solution folders are virtual folders and that there are no folders in file system for them).
4)
We try to keep the number of projects limited because a large number of projects has a negative effect on build performance. Therefore we wouldn't arrange our project the way you suggest in your post (propably). Keep in mind that assemblies are a deployment unit, nothing else. There is no problem in packing several components into a single assembly, as long as they are deployed together. Requirements on releasing individual components can however be a reason to seperate components into different assemblies.
5) For each project we habe an additional unit test project to seperate the tests from production code. We use a naming rule: for project MySystem.MySubsystem.MyWhatever.dll exists a MySystem.MySubsystem.MyWhatever.Test.dll. This simplifies out NAnt script for building, testing and releasing our software.
6)
Namespaces are hierarchical and should be used in this way. That means that we express abstractions with namespaces. E.g: MySystem.MyComponent contains everything that is used in that component and MySystem.MyComponent.MyImplForCaseX contains the details for a specific extension while the code in the subnamespace can access the content of its parent namespace.
This results in very little access to sibling or child namespaces, thus supporting loose coupling of components.
7)
We use subversion as version control system. With the following structure (this is however really project specific):
root/
trunk/
doc/
source/
libs/ contains all 3rd party dlls our projects reference, built up with svn-externals and real dlls
scripts/ contains all NAnt scripts for building, unit testing and releasing
tools/ tools used for building etc.
releases/
Release 1.0/
[trunk/] only if release is modified (bug fixes)
[releases/] "
That's all I can recall on a Sunday Morning 
-^-^-^-^-^-^-^-
no risk no funk
|
|
|
|
|
|
Hi,
Can anyone suggest how to design application, which support multiple databases (like SQL Server, Oracle) and with minimum change, we can shift database from one to another.
Thanks.
|
|
|
|
|
Colin Angus Mackay has nice series about building DAL that supports multiple databases. Swithing from one database to another is a matter of changing configuration file so you don't need to recompile application. You can find the first part here: What is a DAL? [^]
|
|
|
|
|
With most OR mappers this is a change in the configuration file.
Yes, yes I know, if you have performance optimizations in your code, then it's not that easy 
-^-^-^-^-^-^-^-
no risk no funk
|
|
|
|
|
|
heyitsAtul wrote: Hi,
Can anyone suggest how to design application, which support multiple databases (like SQL Server, Oracle) and with minimum change, we can shift database from one to another.
Thanks.
It can be done in several ways. First of all you need to have an abstraction layer. That layer needs to be a generic layer that matches the interface for both databases. Secondarily, I'll recommend that use a factory. Try to take a look at the following link for inspiration
Connection pool[^]
Hth
--
Jess Nielsen, b.sc.
Security Analyst
http://jessn.blogspot.com/
|
|
|
|
|
heyitsAtul wrote: Hi,
Can anyone suggest how to design application, which support multiple databases (like SQL Server, Oracle) and with minimum change, we can shift database from one to another.
Thanks.
It can be done in several ways. First of all you need to have an abstraction layer. That layer needs to be a generic layer that matches the interface for both databases. Secondly, I'll recommend that use a factory. Try to take a look at the following link for inspiration: Connection pool[^]
HTH
--
Jess Nielsen, b.sc.
Security Analyst
http://jessn.blogspot.com/
modified on Monday, November 8, 2010 3:20 AM
|
|
|
|
|
I come across this often, where to avoid round-trips, simple, and even sometimes complex, validations are implemented in JavaScript on the client. Yesterday I put in a little date range validation, which I should really be done at the business layer. However, with the RIA bubble, the single location of the BL on the server is becoming blurred, and somewhat divided between the client and the server.
This brings me to my question about a model for delivering relevant business logic to the client, but not simply by sending custom JavaScript to implement business logic, but using a fixed JavaScript library that uses a rule base shared with the server. Is there any such concept or product?
Do not believe in anything simply because you have heard it. Do not believe in anything simply because it is spoken and rumored by many. Do not believe in anything because it is found written in your religious books. Do not believe in anything merely on the authority of your teachers and elders. Do not believe in traditions because they have been handed down for many generations. But after observation and analysis, when you find anything that agrees with reason and is conducive to the good and benefit of one and all, then accept it and live up to it. (Siddhartha Gautama - The Buddha), 563-483 B.C.
|
|
|
|
|
It is precisely at this point where I turn from web based stuff to smart client applications 
I know there are many advantages to web based stuff, and RIA tech makes them a bit better, but I really never understood the draw to using these for internal business applications.
[edit] ...especially since we have click-once now. [/edit]
|
|
|
|
|
Good call.
Especially with click-once, and especially for line of business apps when you typically control the client environment.
|
|
|
|
|
Hi,
Lets say I have a class called Person with properties Name, Age, Salary. I create a GUI form to show object of this class so users can do CRUD operations on it. Each property will have a textbox for manipulation. However, if my client adds another field to Person, lets say Phone Number, then I will need to modify the database, the data access layer, the class itself, and finally add another textbox to the GUI for phone number. My question is what pattern can I use to handle a situation like above when clients constantly change properties?
I am thinking of using MVC pattern but that will be for other reasons and will not help my question above.
|
|
|
|
|
CodingYoshi wrote: However, if my client adds another field to Person, lets say Phone Number, then I will need to modify the database
If your users are performing CRUD operations, do you even need a Person class? Why not perform the operations on the database itself?
As far as adding fields to a table, this represents changing the database schema. That's non-trivial; I'm not familiar with a pattern that somehow hides or manages those kinds of changes. They're fundamental and will require all the work you mentioned.
|
|
|
|
|
The way most "modern" (and by this I don't mean code generators) data layers perform the O/R mapping between the business object definitions and the database is by a set of metadata that describes how the fields match up. So when you add a "Favourite Colour" field, you add the field to the database. Then (either manually or automatically depending on your tool) add the field to your business object, and update the mapping. The mapping is then used to handle the actual queries at runtime.
A basic CRUD form could be generated at runtime using a similar set of metadata. Diamond Binding uses attributes on the business objects to say "this field comes from FaveColor" - you could use a similar strategy to decorate your business objects with "default view/controller" attributes - or chuck this mapping in a seperate file (probably a "technically" better solution than having your model aware of the default view/controller). You could end up with the class being decorated with [DefaultEditor(typeof(AutomagicCRUDController), typeof(AutomagicCRUDView)] and your new Colour field having a [FieldEditor(typeof(ColorPicker))].
Unfortunately I think you'll find that your clients will end up wanting minor changes to every form you show them, and you'll end up with something pretty close to doing it manually anyway. So my pattern tip is "Hire a load of graduates and get them used to the pain of dealing with clients"
|
|
|
|
|
Great. Thanks for the explanation and honesty.
I just thought I might be doing something wrong because a good design should not cause a ripple effect--I guess that is just "theoretically speaking".
|
|
|
|
|
The real problem here is that most clients think that a simple new field is something trivial to add.
But it's not because:
- How should it be presented in the UI (UI Layer)
- Do the validation rules checking the consistency change (Logic Layer)
- compatibility with old data (Logic Layer, DB Layer)
- Persistency impact (behavior of database, growth, indices, replication, transfer to data warehouse) (DB Layer)
And propably some more...
-^-^-^-^-^-^-^-
no risk no funk
|
|
|
|
|
Hrmmmm, it depends on how many business rules are coming with the new data. If a simple "data-only" field is non-trivial to add then you are probably using the wrong tools.
Of course, the client should have signed off on the domain model and user stories by then anyway, so for modifications at this late stage they are probably paying per-hour anyway... :P
|
|
|
|
|
You're right, if it is a simple data-only field, it should be simple. But in my experience, it is very seldom a data-only field (at least at the end when the customer says: "Oh, I thought it was clear that this and that business rules has to be changed because of that new field").
The result is some more iterations
-^-^-^-^-^-^-^-
no risk no funk
|
|
|
|
|
If its me ... I think I would solve this issue by using the concept of metadata ... the concept ! .. Well in this particular case I think I would use reflection and .NET Attributes ... reflection will help me to get the Fields (Person Class Properties) ... and .NET Attributes to determine which Fields shall be used ... for example
public class Person
{
private string name;
[Displayable]
public string Name
{
get { return name; }
set { name = value; }
}
private int age;
[Displayable]
public int Age
{
get { return age; }
set { age = value; }
}
private string officialID;
public string OfficialID
{
get { return officialID; }
set { officialID = value; }
}
}
Now the Displayable Attribute is a custom .NET Attribute you create ... using reflection I can determine whether this Field has the Displayable attribute or not ... and some kind of class will know how to map this class with its Displayable Fields to the UI for example ...
Hard ... but doable ... and in complex applications could lead to problems if its not designed well ... but mainly in rare cases like yours it could work depending on your business.
Sincerely Samer Abu Rabie
Note: Please remember to rate this post to help others whom reading it.
|
|
|
|
|
hi,
This should hopefully be my last question about my future hotel app.
The first time i built it, i made an insane amount of classes to encapsulate printing, and even then printing was messy.
I thought I could use crystal reports, but did a few tests and ran into some problems. It seems like its a nice thing when you want to just pull information straight from your database and print it but turns out pretty cumbersome when I want to use my own business objects as data for a report.
I know I can add a .NET object to the report via the database expert.But, there are problems when I need data from more than one object on a report. Also, I'm not quite sure how I could feed my own data to a chart in a report.
Is there any other printing/reporting scheme I can use? Or is there a particular design used with crystal reports, Printing is a very essential part of my app.
Thanks so much
Gideon
|
|
|
|
|
Previously I have suggested and recommended Logi Reports as a viable alternative to Crystal Reports.
Get it FREE here http://www.freereporting.com/[^] Caution, it is a fairly large download and there are plenty of tutorials and samples there also.
modified 1-Aug-19 21:02pm.
|
|
|
|
|
I used CR for many years and have always pulled the data from the database - just the way I design things I guess. All reports were serviced by a stored procedure so to deploy a new report required a proc and a RPT file, no recompile required. A hotel app will require an enormous number of reports and each customer will want custom reports done.
I liked it BC you could deploy it fairly simply (as opposed to Reporting Services) in a commercial app. I now do corporate work and use RS exclusively.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
thanks so much for replying, but someone on the Microsoft newsgroups gave me a work around with CR.
I make a new typed dataset for each report that I want to create, I have seperate tables for each chunk of data I need printed.Then I design a new report, when I need the data printed I set the datasource to a new instance of the typed dataset with all my data in it!
It works like a charm, also for situations where I've needed Multiple bunches of information all over the place, I use subreports, somehow the dataset passed to the first report is automatically passed to the subreports too, so it works pretty well.
Thanks!
|
|
|
|
|
Hi,
Actually Im a developer, But my Current role is to gathering requirement from user or customer or client .....Because Im working in a small company....
My specific role is to identify the different forms, reports needed for the analysing project.
while analysing forms or reports I need to know what are fields that going to appear on the form or reports...
So I need to interview the clients or user directly.
This is the situation
Now my question is like:
1) First I will probe the client for requirement, AFter that I will identify the forms needed for the project.
2) Now I need to capture the forms fields and what are the logic behind each forms rite, how to do that?
For eg: The client ask you to create a form with radio button, text box, tables, option button, label etc..
Radio button:
So client saying that I need to select 1 field out of 5 fields, So at this situation you can use radio button, But my question is like how to document it from user, And this document is easy to modify and also understandable by any developer to create.
Tables:
So client saying that I need 2 rows 2 columns and this are the heading, So at this situation you can use tables, But my question is like how to document it from user, And this document is easy to modify and also understandable by any developer to create.
So actually I need different kind of template to capture the requirement for Form, reports etc.. from user or clients, or customer....
remember :We are not developing, I just gathering requirement, I need to just document the requirement so any developer can understand and able to create. And also able to understand by client or customer or user to sign off.
Thanks in advance
Shaan
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
