Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VS 2010 and WinForm and VS 2005
Message
 
 
To
18/03/2010 14:05:53
General information
Forum:
ASP.NET
Category:
Visual Studio
Environment versions
Environment:
C# 2.0
Miscellaneous
Thread ID:
01455348
Message ID:
01455530
Views:
28
>>>>>>Hi,
>>>>>>
>>>>>>I suppose that someone here has a beta version of VS 2010. Does VS 2010 include WinForms projects?
>>>>>>
>>>>>>Also, if you install VS 2010 on the PC that has VS 2005 can you use either independently? That is, can you still maintain VS 2005 projects with VS 2005 after installing VS 2010?
>>>>>>
>>>>>>TIA.
>>>>>
>>>>>Yes, although VS 2010 marks the more or less official blessing of WPF over WinForms.
>>>>
>>>>Thank you, Mike. This is exactly why I want to get VS 2010 so I can start learning WPF. I still want to continue working in WinForms for immediate future.
>>>
>>>WPF is also in VS 2008, so it is possible to learn and use it without VS 2010. If you are starting fairly fresh, as I believe you are, WinForms is to an extent going to be throwaway knowledge. Personally I am not crazy about that because it is a much more familiar paradigm than WPF. And I hate XAML!
>>
>>Using WinForms requires great deal of learning of ADO.NET and C# so it is a wasted time only if WPF no longer uses C# or ADO.NET. Right?
>
>As for learning and being productive while you learn, a great deal can function if put in either XAML or in the code-behind. Does it belong there? Most likely not, but in some cases Yes. This is a simple example of how animations could be done in either place, but it proves the point and also at the very end of the (very short) article, includes a good statement as to which code goes where:
>
>Short and sweet:
>
>XAML - design, code behind business logic.
>
>http://dotnetslackers.com/XAML/re-211780_XAML_By_FARR_Animations_Resources_Vs_Code_Behind.aspx
>
>Even this MSDN article specifies it clearly I think:
>
>The primary application-level mechanism for adding a behavior for an object element is to use an existing event of the element class, and to write a specific handler for that event that is invoked when that event is raised at run time. The event name and the name of the handler to use are specified in the markup, whereas the code that implements your handler is defined in the code-behind..
>
>http://msdn.microsoft.com/en-us/library/ms752059.aspx

I will follow the links and read them. But are you saying that you write your business code in XAML too? No place for C#? And what about ADO.NET? Do you use XAML to manipulate ADO.NET objects?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform