sorted by: recent | see : popular

Content Tagged with .NET + frameworks

Being confronted with an occasional bug in a complex system can be quite overwhelming. There are three disciplines that help you to stay strong: 1) Read and learn about your platform and how to debug it. 2) Use tools to quickly get the low hanging fruit. This might be enough in most of the cases to identify the bug. 3) Think out of the box and try to be creative. Build a model, play with it, break it and fix it. In the worst case, you won't have found the cause of the bug, but you learned at least something new about your software.

Looking at possible ways of making a simpler DSL for GUI state machines.

Yesterday I described the Observer Pattern and mentioned that the .NET CLR provides this functionality through events and delegates. Let’s have a look on how to implement this right now. We’re using delegates with generics, the += operator and throwing and handling events.

So, quite some things have changed in jQuery for Asp.net Mvc preview 3, which made me decide to change a lot in the jQuery for Asp.net mvc (jqmvc) too. To start with most radical one: I ditched the ajax.master. This little ‘framework’ does not rely on a special masterpage in your website from now on. Since things have radically changed, I’ll start all over again on how to use this project.

Silverlight 2 Beta 2 has changed the concurrency model for asynchronous communications. In Silverlight 2 Beta 1, asynchronous requests always returned on the UI Thread. This was convenient, since updates to the user interface can only be done via the UI thread. As of Silverlight 2 Beta 2, asynchronous callbacks are fired in worker threads that come from a thread pool: although this potentially allows for better performance via concurrency, it increases the risk for race conditions between callbacks – more importantly, some mechanism is necessary to make code that updates the user interface run in the UI thread.

Should business entities be able to persisted anytime, even when they're not valid?

MVC (the "model view control" pattern) isn't new, but it is new to ASP.NET. If you're like me, you may have been impressed by a demo, but you've probably thought "how does this work in the real world?" I hope to answer that question in this article.

An explanation of how you can use the Service Locator pattern along with dependency injection to make your code more flexible in certain cases.

I just had a great one on one coding learning session with a good friend of mine over lunch. He's trying to take his coding skills to the "next level." Just as we plateau when we work out physically, I think we can plateau when coding and solving problems. That one of the reasons I try to read a lot of code to be a better developer and why I started The Weekly Source Code. He said it was OK to write about this as someone else might benefit from our discussion. The code and problem domain have been changed to protect the not-so-innocent.

Many users have told us that Gaia is great but it feels a little bit too steep on the price. Well, today we have reduced the price with almost 90%. Gaia now costs $49! Meaning you can get a proprietary license of Gaia for the cost of a couple of BigMacs at McDonalds. Or less than a pair of Jeans would cost you.

A YSlow comparison between samples from the popular Ajax controls vendors for ASP.NET

When building applications re-using components that contain functionality that is used in more than one place in that application is best practice. More than that it is one of the fundamentals of OO development. What about with the MVC framework? Can we use Controls, or UserControls? Because the MVC Framework does not use ViewState, events can not be used, so how do we use these Controls with the MVC Framework? With the MVC Framework at this moment in time we can use the MVCToolkit, this Toolkit has UIHelpers, with these UIHelpers it is easier to create Textboxes, Dropdownlists, RadioButtons etc in the View.

This week at TechEd Microsoft announce the Velocity project, a distributed in-memory object caching system, which got folks like Dare and ScottW talking about using a distributed caching solution for boosting the performance of web sites. That got me thinking more about the differences between Cache and Session State. Although they seem to be the same, and often caching solutions are used for storing session data, I'm not a big fan of putting session in a cache solution

Great, in-depth discussion of when it makes to sense to use LINQ in LightSpeed 2.0.

Having talked about the pain of capturing image snapshots, someone mentioned Cropper and its plug-in model so I thought I'd have a bash at creating a plug-in to optionally re-size on capture. Using these helpful articles (here and here) on using the GDI+ System.Drawing classes to do image re-sizing I was able to pull something together pretty quickly. I modified the Cropper Clipboard Format plug-in to optionally re-size to a user specified width/height using InterpolationMode.HighQualityBicubic for image reduction.

I've wrapped up and tested a handful of ExtJS skins/themes that works with Gaia and added them up for download here with screenshots for those interested.

First thing you should always keep in mind is that with WPF the GDI age is over. You don't need drawing and rendering everything from code. This brings out that something like PropertyGrid control is now nothing more but a collection of brushes, data templates and the most simple steps introducing the desired layout. It might take about 5 or 6 hours implementing the same control from the scratch assuming you already have styles/themes for the controls.

A few months ago, when I installed Visual Studio 2008 on my system, I opened one of my projects, did the usual project conversion, edited some files, created a few others, saved, tested, and checked in source control. Another developer working on the same project, also with VS2008, later edited some of the same files I had edited.