UPDATE: I’ve gotten feedback from folks that I should remind everyone that there is now a Dynamics CRM 2011 Script# Xrm.Page library.

Script# (aka ScriptSharp) allows you to write C# code that compiles into JavaScript.  If you aren’t familiar with it, please watch this video first:

http://channel9.msdn.com/events/mix/mix11/HTM16

I’ve been a fan of Script# ever since it was announced.  However, in my previous role, there were a ton of higher priority technologies for me to cover.  I just never got around to Script# evangelism.  Well now that I am focusing on Dynamics CRM 2011, I have a reason to talk about it.  Script# isn’t for everyone, but those who spend enough time using it tend to swear by it.  In this video, I walk you through two core usage scenarios for Script# in the Dynamics CRM 2011 context:

  • Creating JavaScript web resources
  • Sharing basic logic across server-side code (plugins/workflow activities) & client-side code (JavaScript web resources)

Think of this as an alternative approach to producing JavaScript code for Dynamics CRM 2011.  I tend to like it for all the same reasons the Script# home page calls out: Intellisense that works!, MSBuild Support, Visualize your Code, Intuitive OOP Syntax, Unit Testing Support, Create Documentation, FxCop Code Analysis.  Yes, there are ways to do these things with JavaScript, but Script# lets you use what you already know if you are a C# developer.  If after watching this video, you decide it’s not for you, then erase it from your memory banks and continue with your current approach.

NOTE: Sorry about the audio quality (echo).

@devkeydet