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 07. 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.
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.