Developing Rage

Rage is a complex application that is developed in WPF on the .NET Platform. Rage is also cross-compiled to the Silverlight 5 platform. The majority of the core source code of Rage is shared between the two platforms.

Development Environment

Most developers familiar with the Microsoft platform will already be setup for WPF development. You will want to verify the following checklist prior to working with Rage source code:
  1. Install .NET Framework 4.0
  2. Install Visual Studio 2010, or Visual C# Express 2010 (not all development features may be available)
  3. Install Visual Studio 2010 SP1
  4. [OPTIONAL] Install the Team Foundation Server Client Tools to enable integrated source control access to CodePlex.
  5. Restart
  6. [OPTIONAL] Install Microsoft Expression Blend 4 if you wish to have access to a more feature-rich XAML editing experience when working with Rage's UI.
  7. Open the Rage.WPF.sln Solution file in Visual Studio.
  8. Right-click the Rage.WPF project and choose "Set as Startup Project..."
  9. Hit Play (F5) to start debugging.

Silverlight Development Environment

Most developers are probably not setup for Silverlight development yet, so here's how to set things up:
  1. First, perform the steps listed above for WPF development.
  2. Install Silverlight Tools -
  3. Install the Silverlight 5 Toolkit -
  4. Restart
  5. Open the Rage.sln Solution file in Visual Studio.
  6. Right-click the Rage.Silverlight.Web project and choose "Set as Startup Project..."
  7. If you use a default web browser other than Internet Explorer, choose ONE of the following:
    1. Make VS always use IE for debugging: Right click on Default.aspx in the Rage.Silverlight.Web project, and choose "Browse With...". Select Internet Explorer, and click Set Default. Hit OK. VS will use IE when you debug now, instead of your OS-wide default browser, whatever that may be.
    2. Or if you want to debug in your normal browser, you can, it just may be a bit complicated. I use Chrome, which uses a different process for each window, and one master process. Unfortunately, when you start debugging, VS will attach to the master process, but it's the process for the new window that actually is running the Silverlight code, so you have to goto Debug > Attach to process, and choose the one running Silverlight. It's annoying having to do that all the time, but it works. I think Firefox will work normally as well, but I'm not sure.
  8. Go to Rage.Silverlight/App.xaml.cs, and put a breakpoint in the Application_UnhandledException method. That will be hit whenever there's an unhandled exception.
  9. Hit Play (F5) to start debugging.
  10. The first time you start debugging, it'll ask you if you want to use Silverlight Debugging. Choose Yes.
  11. You should now have Rage running in your browser, fully debuggable. Note that you can't use Edit and Continue, so you have to recompile and relaunch after making changes.

This software uses SharpZipLib

Last edited Jul 4, 2012 at 6:37 AM by Jothay, version 5


No comments yet.