We pay for user submitted tutorials and articles that we publish. Anyone can send in a contributionLearn More
In this post I want to show you how to use jQuery to create an AJAX login screen. I am going to use an ASP.NET MVC application for this demonstration. I will be modifying the small default application that is created when you create a new MVC application. So go ahead and create a new MVC application. I will be walking through the process step by step so when this article is done you will have a working application.
This weekend I typed Dev102 on google just to see what I will get and guess what? We have joind the big league We have site links!! This is what you get when you type Dev102 in Google:
Now all we have to do is get the links to point to the interesting stuff.
Well we’ve arrived at the last part of our series on ASP.NET MVC. In this post we’ll be looking at Views, ViewData, and HTML Helpers. We’ll be discussing how to call Views from Controllers and how to use HTML Helpers to create your markup.
Suppose we receive the following request; http://yourdomain.com/Task/Show/23. The request would map to the following controller.
A while ago Shahar wrote an article about whether WPF Data Binding is Thread safe. Shahar’s findings were that Even if you change a property from a different thread the PropertyChanged event will be called on the UI Thread making Binding Thread Safe.
I have created a Window with 2 TextBlocks, one of them is binded to a Dependency Property and the other is binded to a regular property:
Where do you locate your convertors? do you put them in the Window.Resources section? or in the UserControl they are being used for? Neither of these options is good. You should put it in the App.Xaml file and here is why:
Lets look at the following example:
Here is our Window:
Hey all, Check out the top right corner of your screen! Dev102 has hit 1000 RSS readers!!! Thank you all for reading The Dev102 team.
While working on a complex UI application in WPF I noticed that because I was using DataTemplates both the Xaml and the Code Behind got very messy, that is because if you need to implement some events in the code behind you basically “mix” code from the template and code from the Window, plus you cannot access the elements in the template from the code behind.
Let’s look at the following example:
Copyright © 2012 Dev102.com
Breeze : Designed by Amit Raz and Nitzan Kupererd