I'm interested to know any strategies people have taken regarding Use Case Controller classes and interactions with WinForms. How are your Use Case Controllers structured (methods, etc) Does a Controller class have an aggregate member that is the Form or vice-versa How do you handle Use Cases that span several different WinForms Thanks for any general ideas/solutions you might have.
-Smoke
Use Case Controllers and WinForms
Hot Topic
- TaskVisionWS DataSet(xxx).vb
- Windowing Feature Implentation
- How do you navigate a webbrowser control in another form (c#)?
- Form Synching with DataBound ComboBox
- Fotovision Enhancement
- custom word-processor like control
- TextBox with Bookmark
- Custom Control Click Event
- PictureBox ImageChange Event???!!
- DataGridView CurrentRow Not Being Set
Windows Forms
- How to populate a listbox with a complicated query
- inherited controls
- Using Win32 API to get mouse click
- Controls on tab pages
- how can i programaticaly delete the selected item (row) from a listview with 3 or more columns ?
- Application Not Responding
- Build Errors - Is this a bug in Visual Studio?
- Local and remote databases - disconnected apps
- Report with bitmaps
- MDI Child closed but MDI parent think other
Use Case Controllers and WinForms