I want to help Windows Forms developers transition applications
to Silverlight and WPF. To do that, it will help me to understand
the types of applications that are being maintained or newly
developed in winforms today.
- What does your windows forms app do? Can you describe its key
- Where is your database access happening?
- ADO.NET calls from the code-behind for the form?
- Same project, but encapsulated into a class?
- XML data?
- Do you integrate with other services in the organization? If
so, what and how?
- What types of security authentication approaches are you
- Windows authentication using single sign-on?
- Custom authentication tables in your database?
- Integrate with ASP.NET membership?
- Something else?
- How do you handle authorization in your applications?
- Field-by-Field security?
- Function or button-level security (ie, need privs to do an
update, but not a read)?
- Where is your application logic and rules?
- It's in the code-behind!
- I'm using a business rules framework like CSLA or something
- It's encapsulated in classes on the client
- It's in services on one or more servers
- Have you tried moving to Silverlight or WPF? If so, what were
the things that tripped you up?
- If you had the chance to ask for 3 things you'd like Microsoft
to provide (specific guidance, source examples, templates etc.)
what would you like us to give you to make your migration easier?
Please be as specific as you can.
Help me help you. Answer as many of the
questions above as you can, in the comments below. This is going to
lead into content (talks, videos, posts etc.) and perhaps even
tooling and templates to help make the transition easier for you.
Anything which is a Silverlight feature request or WPF feature
request should go on those sites.
Please share this with the other developers in your
organizations, your customers etc.