I'm Back
After a long, long break from blogging, I am back!! For a while I have been using/learning Windows Presentation Foundation. I find this feature of .NET 3.0 to have huge potential for changing, enhancing the way user interfaces are designed and implemented for applications.I have been using VS 2005 with the Visual Studio 2005 extensions for .NET Framework 3.0. concentrating on standalone applications (the traditional Windows Forms application development that we all know and love)
The good news is that I am able to leverage my knowledge of Visual Studio in order to get right to work creating .xaml to define the UI along with implementation of business intelligence code (usually in VB.NET). Actually when beginning to learn/experiment with Windows Foundation Presentation, which more then likely means being exposed to XAML (eXtensible Application Markup Language) rather quickly, keep in mind what I like to think of as ".NET/Visual Studio" patterns.
For example in a VS 2005 NET Framework 3.0 Windows Application, when adding a new WPF Window to a project results in 2 files being added to that project, one for the xaml (aName.xmal) and one for managed code (i.e aName.xaml.vb). These files are associated with one another - in the xaml file the user interface is defined using XAML, while in the.xaml.vb file holds any associated managed code.
For ASP.NET Web developers this mirrors the "code-behind" approach; user interface defined in .aspx using HTML and code in the associated .aspx.vb file. As is the case with ASP.NET, you could decide to keep code (VB or C#) along with the XAML in the same .xaml file. This is analogous to an in-line ASP.NET approach.
My point here is to keep in mind familiar concepts and patterns about .NET and Visual Studio as they will appear quite often while learning WPF. Recognizing them will help speed up the learning curve.
posted by Gary Gumbiner, MCT, MCPD, MCSD .NET @ 12:15 PM
0 Comments:
Post a Comment
<< Home