I am an ASP.NET / C# web developer.
How much time does it take to learn how to build desktop applications using C# in the .net environment?
Tell me more
×
Programmers Stack Exchange is a question and answer site for
professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.
|
|
|||||
|
closed as not constructive by Jim G., Walter, Yannis Rizos♦ Apr 12 '12 at 13:09
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
|
If you already know asp.net & C#, it shouldn't take much more then a week to get pretty advanced in winforms. WPF has a bit more of a learning curve with all the XAML stuff. Probably the harded change will be getting your head around Threading. |
|||||
|
|
Lareau. Threading is very useful for web apps too. I think threading has a learning curve because source files are viewed in a "single thread" manner with your eyes scanning down from top to bottom. The concept of threads conflicts with the "single thread" eye scan of source files. |
|||
|
|
|
I started from basically 0 experience programming march one year, to learning AHK then to learning console apps and basic C# syntax in May then to writing a full fledged windows forms program by the end of August. That also included time to learn enough php and mysql to set up a functioning facebook application to manage accounts and logins for the program. If you have any serious web app experience then you'll find windows forms a breeze. Also I can't recommend head first C# enough as the bulk of what they cover is using windows forms. =) |
|||
|
|
|
I find developing WinForms applications substantially easier than Web applications (in my case, ASP.NET MVC 3). It is much easier to make a sophisticated UI in WinForms. With Web applications, it's basically tons of CSS and JQuery. |
|||
|
|
|
It's a piece of piss. You just need to spend a few hours with a form designer. Everything will seem pretty unsuprising and slightly easier. |
|||
|
|
|
I'm assuming you mean ASP.NET web forms (as opposed to ASP.NET MVC). If so the transition should be easy. The ASP.NET web forms model was designed with windows forms programmers in mind, which made it very clunky given the stateless nature of the web. In windows forms you don't have these limitations. You don't have a life cycle that runs every time the page is reloaded. State is much much easier to maintain. And you're not limited to what HTML and JavaScript can render. |
|||
|
|
