Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Windows Forms
  4. Windows Forms Development Architecture

Windows Forms Development Architecture

Scheduled Pinned Locked Moved Windows Forms
csharpwinformsarchitecturehelp
4 Posts 4 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    PJ_12345
    wrote on last edited by
    #1

    Hi, If I am looking at developing a new windows forms Application VB.Net 2005 Some Things to look at is why not develope it in a alone standing exe why all these DLLS, What would be the best Architeture using Plain windows forms application to connect to a central data source with massive data being transfered to the client or using dot net remoting ?? Well I am new to the windows applications arena any help would be appreciated. Best regards P

    C B K 3 Replies Last reply
    0
    • P PJ_12345

      Hi, If I am looking at developing a new windows forms Application VB.Net 2005 Some Things to look at is why not develope it in a alone standing exe why all these DLLS, What would be the best Architeture using Plain windows forms application to connect to a central data source with massive data being transfered to the client or using dot net remoting ?? Well I am new to the windows applications arena any help would be appreciated. Best regards P

      C Offline
      C Offline
      Christian Graus
      wrote on last edited by
      #2

      Just like a web app, if you've got serious database work going on, it's best to build a data layer, which will be in a dll. The business rules I'd be less likely to put in a dll, if I was writing a windows app, but I would use namespaces to create that seperation still.

      Christian Graus - Microsoft MVP - C++ "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )

      1 Reply Last reply
      0
      • P PJ_12345

        Hi, If I am looking at developing a new windows forms Application VB.Net 2005 Some Things to look at is why not develope it in a alone standing exe why all these DLLS, What would be the best Architeture using Plain windows forms application to connect to a central data source with massive data being transfered to the client or using dot net remoting ?? Well I am new to the windows applications arena any help would be appreciated. Best regards P

        B Offline
        B Offline
        Brady Kelly
        wrote on last edited by
        #3

        If you must favour a single application, then you should still follow Christian's advice below, and keep your data access and business logic in separate classes, used by your forms. Basically, all your forms should do is respond to UI events, and populate controls.

        1 Reply Last reply
        0
        • P PJ_12345

          Hi, If I am looking at developing a new windows forms Application VB.Net 2005 Some Things to look at is why not develope it in a alone standing exe why all these DLLS, What would be the best Architeture using Plain windows forms application to connect to a central data source with massive data being transfered to the client or using dot net remoting ?? Well I am new to the windows applications arena any help would be appreciated. Best regards P

          K Offline
          K Offline
          kuyak2000
          wrote on last edited by
          #4

          Have you tried one of Microsoft's own best practices such as Enterprise Library 3.1 that combined with Composite UI Application Block (CAB)? This will provide you the best practices, application blocks and hence, good architecture (which is already used and tested by others) to start. This is the link: http://msdn2.microsoft.com/en-us/practices/default.aspx[^] best regards, Eriawan K. :)

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups