Re: Complex Windows Applications in C# -- how high is the bar?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi,




"Norm Powroz" <nep.remove.this.part@xxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:401fp3p524ep6rab35ddeg4lo78uhsngs9@xxxxxxxxxx
Obviously, this is kind of a newbie question, but bear with me...


Now the issue -- I need to carry out some major work on this
application in order to stretch it to handle an enitrely new database
structure. Because of some philosophical changes in the database
structure, it will be easier to scrap the existing application and
build a new one from scratch.

So basically you are going to create a new app from scratch.

This leaves me with a decision -- do I reimplement in C++/MFC/ODBC, or
should I take advantage of new toys, and either target Managed C++, or
shoot the works and do it in C#. I am not a C# virgin, but neither do
I have the same level of confidence/competence with it as I do with
C++. I know that the basic program logic will be completely portable,
and the database bits can all be handled with either ADO.NET or LINQ.
My main concern is the GUI -- this is a very complex application in
terms of its user interaction, since it reduces the construction and
maintenance of a large database to drag-and-drop simplicity by way of
the user interface.


It depends a lot of your expertise, if you are going to build it and you do
not have that much experience ni C#/.NET it would be slower than if you do
it in C++ (assuming you have experience on it).
Regarding the GUI , I have never have experience implementing very complex
interfaces but IMHO it should be at least the same doing it in C# than in
MFC, an uninformed opinion of mine is that it should be easier in .net than
in MFC.

I have dabbled with both WinForms and WPF, but I am still uneasy about
how "down-and-dirty" I'll be able to get. Therefore, I am open to
suggestion, comment, opinion, flames, recommendations...any
information gladly accepted with thanks.


WPF is a completely different approach to buildnig apps, not sure how
easy/fast it's to build a complex interface like the one you need. IMHO WPF
is more oriented to "new media" interfaces. not for something like VS


--
Ignacio Machin
http://www.laceupsolutions.com
Mobile & warehouse Solutions.


.

Relevant Pages

  • Re: Beginning C# Q
    ... starting out with a network app0lication, you have an awful lot to swallow. ... Designing your database is therefore, not quite the first step, particularly ... Groups table, which defines which Groups users belong to, and a Permissions ... That is why an Interface is called an Interface. ...
    (microsoft.public.dotnet.framework)
  • Re: Transaction Oriented Architecture (TOA)
    ... If one builds the application around the database view, ... The problem solution should not have to know about mechanisms like SQL query construction, optimizations like anticipatory caches, or encoding/decoding of dataset formats. ... Note that the CRUD/USER environments already provide exactly that encapsulation by providing a Data Layer that is isolated from the rest of the application through an interface. ... TOA/TOP proposes the database and its application domain stored procedures are the only persistence mechanism necessary, and that the benefits of a focused, single, data-permeable gateway between application and database far exceed the benefits of O/R mappings--regardless of abstraction--and that its lightweight appearance shouldn't be dismissed as missing heavyweight kick. ...
    (comp.object)
  • Re: Transaction Oriented Architecture (TOA)
    ... I don't think the issue is ignoring the database; it is recognizing that the database is a different subject matter applying different business rules than the problem solution. ... There is nothing to prevent abstracting the database subject matter in a classic OO manner with objects like Schema, Table, Tuple, and Query. ... I'm of the opinion that the more obvious the database (or at least its interface) is the more easily maintainable an application becomes. ... I've nothing against creating frameworks and patterns to facilitate those programming activities, but prefer the concept of a problem domain transaction to language-specific expressions mapping 1:1 with anything physically present in the database. ...
    (comp.object)
  • Re: OOP style
    ... Component classes have all their main logic in a Custom base class ... database access unit if they didn't already start with a full DB layer; ... My latest application started with an extensively designed object model ... Typing in the implementation of the database interface is ...
    (comp.lang.pascal.delphi.misc)
  • Re: OOP/OOD Philosophy
    ... You appear to assume that, in order to isolate the database from the gui, ... the GUI layer uses a specific interface of the business ... This is where you need to place logic against the data structure that ...
    (comp.object)