NCache Distributed In-memory Object Cache
July 11, 2010
In my last post I discussed how you can setup Windows AppFabric Caching and use it from ASP.NET MVC.
AppFabric isn’t the only tool out there that provides you with a distributed in-memory object cache. NCache from Alachisoft is another excellent product which can solve your caching issues.
Let’s see it in action…
Windows Server AppFabric Caching
July 4, 2010
For those of you who haven’t heard about AppFabric yet, check out the Windows Server AppFabric Learning Center on MSDN. The first version is out now and can be downloaded here.
One key functionality of AppFabric that caught my attention was its caching feature also known as Velocity (Project Code Name). To quote MSDN:
“For Web applications, AppFabric provides caching capabilities to provide high-speed access, scale, and high availability to application data.“
Sounds interesting, especially as I am building a web application which is going to be hosted in a web farm. Instead of using ASP.NET’s built-in caching option, which is tied to a single AppDomain and thus one web server, I can opt to use a cache powered by AppFabric which is shared across web servers.
Let’s see it in action…
Silverlight Asteroids Part 9: Explosions
June 27, 2010
The spaceship is armed and can blast away at the asteroids. But as it stands now, the asteroids just disappear when they are hit by a bullet. Let’s put a cool explosion effect in the game.
To make this happen we’ll have to introduce an animated sprite into the game which simulates an explosion. Download the source code for part 8, open it in Visual Studio 2010 and let’s blow some stuff up.
Time to put the last finishing touches on the collision detection algorithm that we introduced in the last part of this series. The current algorithm that is in place functions correctly but sometimes you get a feeling that something is not quite right.
At the moment each sprite has a bounding rectangle and when one sprite’s bounding rectangle intersects with another sprite’s bounding rectangle we flag it as a collission. An image says more than a thousand words, so let’s see what can go wrong with this approach.
Figure 1 – Intersecting Bounding Rectangles
As you can see the sprites bounding rectangles intersect, but the spaceship and asteroid do not actually collide with each other. Let’s see how we can improve on this design.
Silverlight Asteroids Part 7: Collision Detection
May 24, 2010
In the last part of this series we finally armed the spaceship. It is now able to fire bullets. However nothing happens when a bullet hits one of the asteroids or if one of the asteroids hits the spaceship. Let’s add some simple collision detection algorithm that notifies us when such crashes occur.
Download the source code for part 6 of this series and open it up in Visual Studio 2010.
Let’s get started…
Silverlight Asteroids Part 6: Fire!
May 7, 2010
In the previous part we finally added some asteroids to the game. Those pesky rocks are now floating around in space, at record breaking speed, forming a major risk for our spaceship!
Time to arm the spaceship so it can defend itself. A gun loaded with high-velocity, copper-plated, hollow-point bullets will do the trick.
Just like a spaceship or an asteroid a bullet represents a sprite in the game. To weaponize the spaceship, you’ll need to follow the exact same steps as you went through earlier in part 2 and 5.
Let’s get started…
Silverlight Asteroids Part 5: Asteroids
May 3, 2010
We’re already at part 5 of the Silverlight Asteroids series. This time, you’ll finally get to hurl some asteroids into space. Just like the spaceship, an asteroid is a sprite. If you remember “Part 2: Sprites“, then you’ll know that in order to add a new sprite to the game you’ve got to follow these steps:
- Add a new Silverlight User Control
- Make sure the user control implements the ISpriteDesign interface (or a descendant)
- Add a new class descending from the abstract Sprite class
- Create a new instance of the sprite and pass in the correct user control as the design of the sprite
If this does not ring a bell, have a quick peek at part 2 first. Without further talk, let’s walk through each of these steps.
Silverlight Asteroids Part 4: Space
May 1, 2010
In the previous part, you finally gained control over your spaceship. Using the arrow keys on the keyboard you are now able to navigate the spaceship anywhere you want.
This Silverlight application has a canvas of 1024 x 768 pixels as its RootVisual, which represents space. As it stands now, your spaceship is allowed to cross the boundaries of this canvas. In this part of the series you’ll find out how you can make the spaceship reappear on the other side of the canvas.
Go ahead and download the code of part 3 and open it up in Visual Studio. If you haven’t read the first three parts of this series, I encourage you to read those now.
Silverlight Asteroids Part 3: Keyboard Control
April 28, 2010
If you haven’t read the first two parts of this series, I encourage you to read those. At least have a quick browse so that you know where we left off.
At the end of part 2 we created a sprite for our spaceship and launched it into space. However it’s engine is not responding to our commands and it’s just floating in space motionless and silent.
Let’s learn how we can use the keyboard to control the spaceship. Download the source code for part 2 and open it up in Visual Studio.
Let’s kick start the spaceship’s engine…
Running ColdFusion Code in .NET
April 25, 2010
Converting one development environment to another can be a painstaking process. You’ve got to take all the code that took months, years to write, test, tweak…etc. and rewrite it in another language. Hopefully after you are done the new code base will pass all of the testcases.
Wouldn’t it be handy if your new development environment provided a way so that you could utilize libraries, components written in the old language? This way you can leverage the power of these existing parts while you rewrite other parts of the application. As time goes by and releases are build you can phase out these parts.
Using the old libraries for certain aspects of the application, you can cut down on costs and development time. Management likes to see progress periodically, especially after you’ve decided to move to a new development environment. And you can gradually ease the transition for the development team as they acquire new skills while still utilizing their existing knowledge.
Let’s make a test case, showing you how to ease the transition from ColdFusion to .NET.






