.NET Framework 3.5
Source Code Part 1: The Bootstrapper Part 2: The Shell Part 3: Regions Part 3b: View Injection and The Controller Pattern Part 4: Modules Part 5: The View-Model Part 5b: ServiceLocator vs Dependency Injection Part 6: Commands Part 6b: Wrapping IClientChannel I wasn’t originally planning on a post specific to this topic, and there is likely some rehashing...
Source Code Part 1: The Bootstrapper Part 2: The Shell Part 3: Regions Part 3b: View Injection and The Controller Pattern Part 4: Modules Part 5: The View-Model Part 5b: ServiceLocator vs Dependency Injection Part 6: Commands Part 6b: Wrapping IClientChannel I have to apologize for the length of this...
Source Code Part 1: The Bootstrapper Part 2: The Shell Part 3: Regions Part 3b: View Injection and The Controller Pattern Part 4: Modules Part 5: The View-Model Part 5b: ServiceLocator vs Dependency Injection Part 6: Commands Part 6b: Wrapping IClientChannel ...
Source Code Part 1: The Bootstrapper Part 2: The Shell Part 3: Regions Part 3b: View Injection and The Controller Pattern Part 4: Modules Part 5: The View-Model Part 5b: ServiceLocator vs Dependency Injection Part 6: Commands Part 6b: Wrapping IClientChannel Alright, so we’re finally here. I could...
Source Code Part 1: The Bootstrapper Part 2: The Shell Part 3: Regions Part 3b: View Injection and The Controller Pattern Part 4: Modules Part 5: The View-Model Part 5b: ServiceLocator vs Dependency Injection Part 6: Commands Part 6b: Wrapping IClientChannel Welcome back to my series on implementing the Model...
Part 1: The Bootstrapper Part 2: The Shell Part 3: Regions Part 3b: View Injection and The Controller Pattern Part 4: Modules Part 5: The View-Model Part 5b: ServiceLocator vs Dependency Injection Part 6: Commands Part 6b: Wrapping IClientChannel In my last post I addressed regions in the Composite...
Source Code Part 1: The Bootstrapper Part 2: The Shell Part 3: Regions Part 3b: View Injection and The Controller Pattern Part 4: Modules Part 5: The View-Model Part 5b: ServiceLocator vs Dependency Injection Part 6: Commands Part 6b: Wrapping IClientChannel This is the third post in a series of...
Source Code Part 1: The Bootstrapper Part 2: The Shell Part 3: Regions Part 3b: View Injection and The Controller Pattern Part 4: Modules Part 5: The View-Model Part 5b: ServiceLocator vs Dependency Injection Part 6: Commands Part 6b: Wrapping IClientChannel This is the...
Source Code Part 1: The Bootstrapper Part 2: The Shell Part 3: Regions Part 3b: View Injection and The Controller Pattern Part 4: Modules Part 5: The View-Model Part 5b: ServiceLocator vs Dependency Injection ...
Below is a link to both the source code and my slide deck from Utah Code Camp on Saturday, Sept 19, 2009. http://dl.getdropbox.com/u/273037/CodeCampMVVM.zip I will be posting follow ups to this presentation over the coming weeks. I should be able to post at least once a week covering the topics in detail For those who attended, please let me know which specific topics you’d like to hear about first or if you have any questions you’d like to see addressed.
Source Code I’m working on a Silverlight scheduling application and wanted to make the DatePicker control from the Silverlight Toolkit look like the program icon on my iPod Touch. The calendar looks icon like a day calendar and dynamically displays the current date. I got the idea when I was looking at the calendar icon on the right-hand side of the DatePicker control. It was actually one of those accidental ideas. The control’s icon looks like a day calendar and displays the number ‘15’ – well the day I was looking at it happened to...
Let me start by saying I have no qualms against using var to declare variables. I use it myself when it suits me. I find the best situations to take advantage of it are: When using anonymous types When declaring variables which are instances of an interface The first case is really not optional. You can’t declare an anonymous type without var. The second, should be used carefully because it can impede readability if used incorrectly. Since you cannot initialize an interface the right side of your declaration might...
This is the fourth and final article in a four part series on building a single sign on (SSO) provider using the ASP.NET platform. Make sure to check out part 1, part 2 and part 3.Source CodeImplementing a Single Signon ProviderThis is all a rehash since I've covered each point in detail to this point, but I'd like to tie everything together at this point and provide the source code. If you'd like detailed descriptions about how/why review the previous 3 parts. The full source code will be available here. When an unauthenticated client requests a secured resource...
Using JSONP with WCFThis is the third article in a four part series on building a single sign on (SSO) provider using the ASP.NET platform. If you just want to know about JSONP and WCF and aren't interested in implementing SSO read ahead. Otherwise, make sure to check out part 1 and part 2. (Part 4 and the source code are now available).JSONPAlso known as “JSON with Padding” is more of a back door to allow cross domain AJAX requests. By dynamically generating <script /> tags in the current page it gets around the “Access to restricted URI denied” error...
Using Forms Authentication with WCFThis is the second article in a four part series on building a single sign on (SSO) provider using the ASP.NET platform. If you just want to know about forms authentication and WCF and aren't interested in implementing SSO read ahead. Otherwise, make sure to check out part 1 (part 2, part 3, part 4 and the source are now available).IntroductionAn important distinction to make here before I get started is that I am not using FormsAuthentication to secure a WCF service. I am using FormsAuthentication to manage user identity. FormsAuthentication comes with handy Encrypt/Decrypt methods...
This is the first in a 4 part series on building a single sign on provider using the ASP.NET platform (ASP.NET and WCF). Originally, I wrote the article as a single post but it was pretty long, even for me. Part 1 addresses the problem in general and how I decided to architect it. Part 2 discusses setting up FormsAuthentication for WCF Part 3 discusses JSONP communication between the client and WCF Part 4 describes the implementation details and includes the source code. Part 1: Planning an SSO Solution We're using a custom...
<add name="AdventureWorksEntities" connectionString="metadata=.\AdventureWorks.csdl|.\AdventureWorks.ssdl|.\AdventureWorks.msl; provider=System.Data.SqlClient;provider connection string='Data Source=localhost; Initial Catalog=AdventureWorks;Integrated Security=True;Connection Timeout=60; multipleactiveresultsets=true'" providerName="System.Data.EntityClient" /> According to MSDN, the above EntityClient connection string will search in the following locations for the specified csdl, ssdl and msl resource files: The calling assembly The referenced assemblies The assemblies in the bin directory of an applicationHowever, I have not found this to be...
As a general rule I prefer to avoid referencing System.Web in my library classes. But if it can't be avoided it's still a good idea to avoid the use of HttpContext.Current. It must be nice to live in a perfect world you say? Yes, there are times that even this cannot be avoided. Or can it? Yes, it is possible by wrapping HttpContext.Current with a helper library which exposes only the methods required by your library. But there are times when even this is an arduous task at best. So what's a guy to do?System.Web.AbstractionsWell, it just got easier. If...
I've been playing with the new ASP.NET MVC Framework CTP which uses anonymous types to build url paths which allow you to change the path format. I'm really enjoying the control and the separation of concerns you get.As I've been writing my MVC application I needed to maintain a parameter in all urls for authenticated users but I didn't want to have to manually include the paramter in every url, form action and redirect. So I wrote some extension functions which wrap the Html and Url helper class methods used to build urls (ActionLink, Form and Url). Additionally, I wrote...