Architecture of .NET Desktop Application - Client Server C#, SQL -


Recently I have been given a chance to develop a PMS (Practice Management System) software for a small physiotherapy clinic.

I am a computer science student and my course is mainly told on Linux. However, my client runs all of their computers on Vista or Windows 7.

I think developing a front end of the customer in Visual C # and using a central postgrescle server.

I am starting with Windows programming so I am following advice on best practices for implementing user rights and access levels in C # (WPF or Windows FORM). I have taken a look into the credential class in the Visual C # and Access Control list but please share your thoughts

to expand just:

Use my form of window views By entering the front end and entering the level of admission, the control / tables / form is given to the user to hide.

e.g. The Finance Reporting Form will be displayed to the owner of the clinic only, whereas the Secretary will be shown only the appointment diary form.

So I probably need a dialog that if the user is asked to login to the system, then should I store or map those login details in the database? Are the best use of library or class to handle those tasks?

I'm probably one of those ways on my head, but this is my first commercial project so I'm eager to check water.

Use these tools and techniques for your project.

  • Visual Studio
  • .NET Framework 4.0
  • WPF using MVMM
  • SQL Server 2008 Compact or Express
    • Li>
  • SQL to Linux

    • Some notes:

    Speed ​​PostGrassClin Are you developing on MS, Baby? Will you lap with SQL Server (LASP)? no at all. Do not bother yourself and try to get all the tools and code samples that work with PGRE.

    You can develop awesome software using VS 2010 Express and SQL Server 2008 Express. To buy commercial software either, yes, you can buy VS You lose on some cooler devices, and you are limited to the 4GB database in SQL Server (10 GB R2), but I do not think you'll miss it too much.

    I will definitely start in 4.0. At this point there is no meaning developed in 3.5 and 2008. If you do not achieve anything through development in 3.5, why do you do this? All 3.5 code samples and information still apply to 4.0, but the reverse is not correct.

    The SQL Server compact makes for a simple deployment on a single machine or machines that do not require a central database. Express is good for the rest, do not think that you will need to worry about it.

    At this point I suggest SQL to Linq at Eq4. I am not happy with EF 4 It seems that the crater of success is very small. Like the thunder of success, L2S is easy for beginner developers, Methinks


    Comments

    Post a Comment