Can i use wpf in asp net

Products By Bayt. Use Our Mobile App. Get Fresh Updates On your job applications, and stay connected. Download Now. Start networking and exchanging professional insights Register now or log in to join your professional community. Upvote 1 Views Followers 1. Write an Answer Register now or log in to answer. Upvote 5 Downvote 0 Reply 0. Before we go any further, let's take a look at the application we're going to create.

It's a simple application that reads data from an XML file and displays it in a list. There's nothing complicated going on in it, and we are going to accomplish all the "clever" stuff. The data that we are going to bind to looks like this:. As you can see, there's not a lot to it.

There are a couple of styles that we've added manually to control formatting, but there is no clever code going on here. The binding is all taken care of here for us. I used Expression Blend to put this together hint - if you're serious about WPF, then you really need to get a copy of Blend; it makes your life so much easier. As mentioned before, we created a couple of styles in the ASP. NET application. Similarly, we created a couple of styles in the WPF application, which do roughly the same thing.

In this section, we're going to take a look at the two types of styles we created. In CSS, a type selector allows you to match a style to every instance of this type in the document tree. So, we're going to change the font of every TD element to 10px Tahoma. WPF allows you to do the same by creating a style that is applied to a particular TargetType. In our example, we change the font of every ListBox in the window to size 10 Tahoma. Careful readers will notice that I didn't say that the size of the font in the ListBox is 10 pixels.

This means that we no longer think of things in terms of pixels - so, a 1 inch button on a 96DPI monitor will be a 1 inch button on a DPI monitor. In the ASP. NET application, we created a named style that changed the font to 12px Italic Verdana. In order to apply the style in ASP.

WPF does allow you to create the equivalent of external stylesheets. Josh Smith has provided excellent tutorials on using external resources. My favourite is this one. In both cases, we created a DataSource which linked to the XML file, and then said how we wanted to display it.

In ASP. NET, we declared that we wanted to use a set of BoundField s to display each portion of the data. The WPF we have used here is more powerful because we have separated out how we would like our items to be displayed from the container that will actually display it.

This means that we can use the same template in different containers - thus maintaining consistency, and removing duplication. This states that we want to display one row of data per item, with three columns.

Each item is displayed in a TextBlock , which is a general purpose text class, and is bound to a particular element using one way data binding. In our sample, the actual consumer of this DataTemplate is the ListBox. The ItemsSource tells the runtime that we want to bind the data in the datasource to our listbox.

As mentioned, the Grid in the DataTemplate represents one row of data. The ItemTemplate simply tells the application which template to apply on each row and, to a certain extent, could be thought of as being analogous to the RowDataBound method on the GridView.

So, for each row of data, we're going to create a grid represented in the PersonTemplate. I hope that this article has whetted your appetite enough for you to want to start playing around with WPF.

If you have experience in ASP. NET, and has put this to good use. NET, a lot of the concepts will suddenly fall into place. Obviously, I've glossed over a lot of the details about how to use WPF, and I'm not claiming that WPF should be used for web development, but it shows how that particular mindset can give you a head-start.

The web pages developed using ASP. NET are called Web Forms that carry an. These web forms use XHTML markup language and features like server-side web controls and user controls that help the developers to manage the static as well as dynamic contents on the page. Microsoft has been able to segregate the static and dynamic content on a web form via extensions.

NET is associated with things on the web. WPF can only be used if you have a. NET framework and Internet Explorer installed. WPF takes more time to load pages. NET requires the programmer to have a knowledge of web model, UI. Obviously WPF has out-of-browser capability! And yes, the OOB transition can work identically to Silverlight if you set it up correctly. Silverlight is fantastic , but WPF is even better as long as you don't need to go cross-platform.

WPF is the way to go, without a doubt. I agree with all that Ray Burns has said. Because: You will get a richer, slicker, faster application. It will be easier to build 1. Keyboard navigation is still better with native applications. I've got some thoughts on this I jotted down in my journal entitled Designing a plugin architecture for an application When building a WPF application you will be writing in one language e.

Richard Harrison Richard Harrison Plugin Architecture, for future visitors: MEF is quite easy to use and learn too. Rev Rev 2, 7 7 gold badges 43 43 silver badges 74 74 bronze badges.

Developing asp. Developing Silverlight version is much simpler, because of C ,. Lex: Totally agree. Lex my mean developing silver-light with prism pattern not simple silver light. You better not use Prism then. There are plenty of easier frameworks out there, like Caliburn. Micro or MVVM light. Is your app a desktop app or web app. If Desktop wpf is best. If web based asp. Net web app using jQuery". Thanks though : — Rachel.

Some points to be made for ASP. With multiple locations you might be able to skip a few layers and go directly to a website? Mischa Kroon Mischa Kroon 1, 1 1 gold badge 13 13 silver badges 19 19 bronze badges. I agree about the developer pool, though I don't know how significant that is in this economy. I disagree about the future-proof. NET is getting old, fragile, and bloated. WPF is moving out onto devices in the form of Silverlight. NET will be history. Just thought it would be fun to update on this comment because it was about predicting the future.

NET Core to make it work on all platforms and be less bloated. Silverlight has development cut, but WPF is once again getting updates but they are focused on windows desktop. The Overflow Blog. Podcast Explaining the semiconductor shortage, and how it might end.