Morning Coffee 16

  • Forgot to say this yesterday, but I’m happy the Colts are in the Super Bowl. Well, I guess I’m more happy that New England isn’t in it. They’ve won it enough lately. I wish the Saints has made it, but at least this way I have no question who to root for on Super Bowl Sunday.
  • My Gamerscore cracked 1000 over the weekend. I got 60 points in Dead Rising and 100 points in NHL 07k0%01%02). I have played ten games + three arcade games for a maximum possible Gamerscore of 10,600 and a Gamerscore “conversion rate” of 10.28%. I wonder how good that is? All the leader boards I’ve seen rate purely on Gamerscore.
  • Speaking of games, Obsidian (of Neverwind Nights fame) is working on an Aliens RPG! Check out this post by Chris Avellone of Obsidian on Game Design Research (via Game Tycoon).
  • Richard Grimes’.NET Instrumentation Workshop rocks. Richard also has extensive workshops on .NET Security and .NET Fusion (aka runtime binding). If they’re as good as the instrumentation workshop, they’re worth a read.
  • In my SSB/WF prototypes, I’ve simply been writing to the console. The lo-tech brute force works okay for a console app, but not at all when I move my code into a shared library. So I decided to bite the bullet now and translate the Console.WriteLine calls into TraceSource calls. My prototype isn’t that big (yet), but it went pretty smooth nonetheless. I currently have three TraceSources in my solution – one for the host, one for my SSB activities & workflow service and one for the persistence engine (I just inherited from SqlWorkflowPersistenceService and added the trace calls). I’m sure in time, I’ll wish I had set up my TraceSources differently, but for now it works.
  • The one feature I lost moving from Console.WriteLine to TraceSources was color support. Since I am creating voluminous tracing data, I used color coding to indicate which part of the application the trace information was coming from. Of course, the OOB ConsoleTraceListener doesn’t have any mechanism to color code the output. I hacked up a ColorConsoleTraceListener in a couple of minutes that worked great. I say “hacked” because my color choosing code is currently hard coded, rather than being stored the config file. If I get the time to change that, I’ll post the code here.
  • While researching ASP.NET’s Membership system, I found this Scott Guthrie post with links to ASP.NET providers for MySql, Oracle and SQLite. I’ve wondered about the lack of a simple file-based ASP.NET role/membership provider and even started hacking together an XML based one. But the availability of a .NET SQLite data provider makes that an interesting option. XML would be human readable, but porting the existing SQL providers to SQLite would probably be easier.
  • Politics 2.0 in action: Talking Points Memo is enouraging you (aka Time Magazine’s Person of the Year) to record your own response to tonight’s State of the Union. Basically record your response via camcorder, webcam or cellphone. Then upload it to YouTube and add it to the TPM SOTU group. With President Bush’s approval rating at all time lows, I’m guessing these videos will be venting some of the pent up hostility towards this administration.
This entry was posted by DevHawk on January 23, 2007. It was posted in Morning Coffee and Politics. It was tagged ASP.NET, Instrumentation and Xbox 360.

Comments:

My gamerscore is 9709. I've played 11 Arcade games (many of which have been demos) and 32 retail games. My GS completion rate is 29.15% (30.82% for non-demos). There are some people out there with ridiculous scores.. I don't know how they do it :)
This comment was posted by Tim Marman on January 23, 2007 at 11:54 AM.
If you are still interested in the xml file membership provider approach, then check out this codeplex project ASP.NET XmlProvider Library http://www.codeplex.com/XmlProviderLibrary They got a fairly complete implementation of the membership, role, profile, and personalization providers
This comment was posted by Rich McCollister on January 23, 2007 at 12:04 PM.

Categories

Tags

Series

Disclaimer

The information in this weblog is provided "AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion. Inappropriate comments will be deleted at the authors discretion.