Win32 v Windows Forms v Windows Service

Win32 v Windows Forms v Windows Service

• soulmate75

  Thanks Derek,

  One last question. If I were to create a windows application is using windows forms sufficient Do I need to create another program to interact with the windows forms

  
  
  

• listerg

  Hi there,

  Win32 is just a way of saying Windows 32 bit. In a programming sense Win32 is unmanaged native Windows 32 application compiled to machine code. A program developed to run on a Windows 32 bit machine's instruction set.

  Windows Form is the screen that applications display that contains controls. User's interact with Windows software using Windows forms. There are different variations of the theme. For example a MDI (multiple document interface) is a windows form that hosts other windows forms.

  A windows service doesn't have a user interface. Its an application that continuously runs in the background on a Windows machine. You can provide an interface for a service but this is generally to change settings of the service. The user tends not to interact with the service often.

  
  
  

• Raghavendra Prabhu

  Depends on what your application is going to do mate.

  If you develop with windows forms though then its the user that interacts with the software most of all. The forms become your program. You design your forms and then in the application you display a main form. From that main form the user can navigate through your other forms.

  
  
  
• Win32 v Windows Forms v Windows Service