Infragistics Blog

Microsoft Windows Presentation Foundation (WPF) is a user interface (UI) framework for building Windows client applications with immersive and intuitive user experiences. It is a subset of the Microsoft .NET Framework and was first introduced by Microsoft as part of .NET 3.0. It combines the application UI, 2D graphics, 3D graphics, documents, and multimedia into a single framework to help developers create rich and interactive applications.

Gathering UI requirements is simple right? You just need to ask end users what they want, what they need and from there get on with the business of developing the solution they asked for - whether it’s an app, an Intranet or some other enterprise IT solution. If only things were so simple!

Which is a better method of analyzing user research and usability testing data, typing up your notes in a spreadsheet or creating an affinity diagram?

While the fundamentals of chart design largely concern the accurate and efficient visual representation of data, it is important not to forget the supporting structures - axes, tick marks, tick labels, and grid lines.

Many of the dashboards I come across are beautiful or at the very least aesthetically pleasing, but are they effective dashboards?

This month, Infragistics takes you through the creation of a financial cash flow dashboard using our Windows Forms controls, but without looking like a typical clunky Windows Forms application.

Imagine you want a chart that shows how some whole is divided up among its constituent parts. Popular convention may tell you to think in terms of a pie chart.

It’s usually good practice to have automated unit tests while developing your code. In unit testing, we test the smallest unit of the code for a particular behaviour. The Unit test helps us to find bugs in the code early in the development cycle.

Depending on a project’s size, scope, and requirements, you may have opted to use an ORM such as Entity Framework without further abstraction or encapsulation. Larger enterprise applications may need complicated layering and services, but the development overhead should be justified.