ASP.NET Facebook Starter Kit updated to VS.NET 2010

Recently, I received an email via my blog asking for a VS.NET 2010 version of my Facebook Starter Kit. Since I no longer work on Windows it hasn’t been a high priority so I offered instructions on how to extract the project from the .vsi file and load the project manually. Much to my (pleasant) surprise I got a follow-up email with an updated starter kit for VS.NET 2010 updated to .NET v4.

If anyone decides they want to upgrade the FDT to the latest version I’d be happy to post an update for that as well. The starter kit is available on Facebook is nearing 5600 users! An interesting side note, I’m no longer able to edit the properties of this application on Facebook because it contains the word “facebook” in the URL which is no longer allowed.


Properties of a webform causing inline errors using <%= %> style markup

I’ve been looking at the latest Facebook Developer Toolkit samples and tried to add a property to the Default.aspx.cs using the IFrame sample application like this:

<%=this.MapCanvas %>

Which yielded this error:

Error    28    'ASP.default_aspx' does not contain a definition for 'MapCanvas' and no extension method 'MapCanvas' accepting a first argument of type 'ASP.default_aspx' could be found (are you missing a using directive or an assembly reference?)    C:\Users\SteveT\Documents\Visual Studio 2010\WebSites\FBIFrame\Default.aspx    38    17    C:\...\FBIFrame\

The problem is that the @Page tag reads:

<%@ Page Language="C#" AutoEventWireup="true" MasterPageFile="~/IFrameMaster.Master" CodeBehind="Default.aspx.cs" Inherits="IFrameSample.Default" %>

Changing CodeBehind to CodeFile gets things working.

<%@ Page Language="C#" AutoEventWireup="true" MasterPageFile="~/IFrameMaster.Master" CodeFile="Default.aspx.cs" Inherits="IFrameSample.Default" %>

Debugging ASP.NET Applications on IIS and Diamondback

Since I work on Diamondback (the
next release of Delphi) and
ASP.NET specifically I thought I’d begin to mention some of the ASP.NET
improvements that have been made now that we’ve “given out the bits” at Borcon. 
One area that can be problematic in D8 is debugging ASP.NET applications on
IIS.  While it’s possible to use Cassini as an
alternative development server, using IIS frequently encountered problems.  In
D8, we made our best attempt given the time we had and the fact that MS uses an
undocumented debugging mechanism for ASP.NET applications in VS.NET. 
Regardless, now that we’ve had the time to research the issues more our debugger
gurus have come up with a mechanism that works much better and enables much more
consistent debugging of ASP.NET applications running under IIS from Diamondback.