If you have a WPF screen that is made up of two of more "sections," where each section has its own unique functionality, you might want to consider breaking each of those pieces of the screen into individual user controls and individual view model classes. This will help you build, run, and test each component. You can then aggregate the user controls into one control and inherit from one view model to the other to bring them all together. In this blog post, you are going to build upon the sample created in the post entitled "Basics of MVVM in WPF." Read and download that sample application to follow along with this blog post.
In this blog post, you learn how easy it is to use the Model-View-View-Model (MVVM) design pattern in WPF applications. This blog post is a step-by-step illustration of how to build a WPF application to display a list of users. You are going to perform the following steps.
In the last blog post, you learned to read songs from an exported iTunes XML file. If you have been using iTunes for a long time and have deleted songs, merged songs from other libraries, or moved your library from one computer to another, then you may not know it, but there could be song files on your hard drive that are no longer in your iTunes library. This blog post shows you how to locate those missing files. To follow along with this blog post, read and follow the instructions in the first blog post on reading songs from iTunes.
In an earlier blog article, I discussed why you need a solid demand management process. Demand is what others are asking you to do. It is your “to-do” list or backlog of activities. From this list or backlog, you must be able to select the right work. The other part of what you do for a living is executing the work: doing work right. Therefore, “right work” (what is best to do next) vs. “work right” (what people, processes, or tools will be employed to do the work in the most effective way).
Have you ever wanted to retrieve the list of songs from your iTunes library? Getting songs from iTunes is not easy. In fact, since Apple stopped supplying their COM component for reading from their iTunes library, about the only way to get song data is to export the library into an XML file, then parse the XML. In this blog post, you are going to learn to parse the XML using the classes contained in the System.Xml.Linq namespace.
With everyone blogging about tech trends out there, we noticed that there weren't many talking about trends specific to business and business applications. We have worked with enterprises for over 16 years to solve the real-world challenges that real businesses face. After a very busy 2018 working with all sorts of business across industries, here are the top four business technology trends we noticed. Here's to a happy, healthy, successful 2019 for all!
In this blog series, you have assumed that everything has gone correctly when uploading files. However, if you attempt to upload a file that is too large, you receive an error from your web server. In this blog post you are going to learn how to get the maximum size of file allowed, display that value on the page, handle an error when the file is too large, and modify the maximum size of file allowed. If you have not done so already, please download the sample from Part 5 so you can follow along with this blog post.
So far in this blog post series on uploading files with MVC, you have learned to style the file upload control, use a view model for data binding, create a thumbnail from an uploaded image, and store files on the server's file system. In this post, you learn to store the uploaded file in an SQL Server table. If you have not done so already, please download the sample from Part 4 so you can follow along with this blog post.
You have known about Test-driven Development (TDD) for years. You’re aware that modern application frameworks were designed with testability as a primary concern, and unit testing and continuous integration have become an industry standard. You have a hunch that TDD will benefit your teams, yet you haven’t embraced the practice! You are out of excuses and you may even feel behind the curve. No worries—let’s get you going with TDD.
In any application, you want to keep the coupling between any two or more objects as loose as possible. Coupling happens when one class contains a property that is used in another class or uses another class in one of its methods. If you have this situation, then this is called strong or tight coupling. One popular design pattern to help with keeping objects loosely coupled is called the mediator design pattern. The basics of this pattern are very simple; avoid one object directly talking to another object, and instead use another class to mediate between the two. This class is called a message broker. The purpose of this blog post is show you a simple approach to using a message broker in your XAML applications.