Accepted Into Microsoft BizSpark

Microsoft has this neat little program, BizSpark, that gives a company free access to pretty much all of their products for three years for a total of $100. The idea is that if they can get startups hooked on Microsoft operating systems, databases, and development tools, then if the companies are still alive after three years they’ll become thriving, paying customers.

Seems like a smart idea to me. After all, startups generally have to be run “on the cheap”, so most of them turn to Linux and open source solutions. BizSpark is keeping Microsoft competitive, helping out startups, and is an all-around good thing.

So, my company, Zeta Centauri, Inc., was just accepted into the BizSpark program and I now have access to all these neat development tools, including Visual Studio 2008 Team Suite (which is $10k retail). It’s still downloading, but I’m sure I’ll have to post about some of the bells and whistles that come with it. I’ve never worked with anything above Visual Studio Professional. With any luck these new and shiny tools will help me build something awesome.

A New Laptop

I’ve been meaning to get a laptop for a while. One might say that I don’t need another laptop. After all, I do have five already.

Of course, all five of these have bad hard drives. The newest one is seven years old. One has a blown motherboard. One lacks a power supply. One has a dead keyboard.

So maybe it’s time for a new one.

Newegg.com had a sale on one I couldn’t resist — a Gateway T-6345U Pentium T3400 2.16GHz dual core system with 2GB of RAM and 250 GB hard drive for $399 (normally $549). Since it’s pretty much the same spec as an $800 machine I was considering, it was a no-brainer. I’ve always thought you had to have no brains to buy Gateway, so in this case it was a done deal.

Believe it or not, the hardware doesn’t actually suck. You get a lot for 400 bucks.

It shipped with Vista Home Premium. Resizing the partition to make room for Ubuntu Linux was a bit of a pain — I couldn’t squeeze more than 110GB out of the Vista partiton in the resize, and that was with page files and snapshots turned off and a good solid defrag. And, of course, after all that ridiculous junk that gets bundled with a new PC was removed. Why do they even try to sell people Earthlink dialup?

After trying to install Ubuntu 8.04 and totally botching the partition job (it boots, but can’t login because home directories can’t exist — Whoops!), I’ve thrown in the towel on 8.04 and will be installing 9.04 after it finishes downloading (at a blazing 25kb a second — why do I have this 4 meg high-speed connection again?)

Eventually I’ll have the sucker set up for dual booting Vista and Ubuntu and not long after that, set up for developing Basternae 3 and all of the other web miscellany that I’ve been working on (Django, ASP.NET MVC, etc.)

The Harpers

Believe it or not, before this year I had never read any of the novels in the Forgotten Realms series. I had always been more of a fan of Dragonlance.

Lately I’ve started reading The Harpers series. I started because I read and enjoyed the Dark Sun novels by Troy Denning. Since he wrote the first book in the Harpers series, I decided to give them a try. So far I’m up to the third book, Red Magic, and I’m pretty sure I’m going to eventually end up finishing the whole series.

Of course, I know it’s a gateway drug. Before long I’ll be reading all of RA Salvatore.

Even Weirder Character Names

As if the random name generator from a week ago wasn’t goofy enough, I’ve created a version with umlauts, accents, and all manner of weird-ifying characters added to the mix.

Try it here: Odd character name generator.

Expect some extremely unpronounceable names.

Random Character Name Generator

I wrote a random character name generator in Python today. It’s HERE at Xangis.com.

The system used is:
1. Roll a d6. 1-3 = consonant (1d20). 4-5 = vowel (1d6 with ‘y’ counting as a vowel), 6 = end name.
2. Names must be at least 3 characters long, ignore a roll of 6 if the name is too short.
3. If you get three consonants in a row, end the name.

I used to use that method to generate horrible character names for AD&D a decade and a half ago.

Zone Data Encapsulation Complete

Zone data encapsulation is complete now. It was a long, tedious process, but it’s all for the greater good.

Last time the code was Fx-Copped, It ran 778,249 checks and found 10,850 issues. This time, it ran 865,441 checks and found 10,370 issues. It’s an improvement, but not a huge one.

We now have the power to enforce sanity. For instance, when an object’s condition is set, we cap it at a max of 100% (perfect) and a minimum of 0% (destroyed).

Encapsulation of Zone Data 80% Complete

Just a progress report — things are moving along slowly but steadily and it shouldn’t take all that much longer to finish data encapsulation for the zone data classes.

FindMUD Now At 500 Listings

FindMUD.com has broken the 500 MUD listing mark. It’s growing slowly but steadily.

Pulled Over by FxCop

I ran FxCop against the Basternae source for the first time today. It ran 778,249 checks and found 10,850 issues.

While some of these really are design flaws, some minor and some serious, many of them are not applicable to this project, such as the security declarations and assembly signing. Here’s how I break down what FxCop has complained about:

Applicable issues:
* Array fields should not be read only.
* Avoid type names in parameters.
* Avoid uncalled private code.
* Avoid unnecessary string creation.
* Collections should implement generic interface.
* Consider passing base types as parameters.
* Do not cast unnecessarily.
* Do not concatenate strings inside loops.
* Do not declare visible instance fields. (This is what the encapsulation I’m working on is all about, and was a significant percentage of what FxCop complained about.)
* Do not initialize unnecessarily.
* Do not name enum values ‘Reserved’. (This was a surprise.)
* Do not pass types by reference.
* Do not raise reserved exception types.
* Enums should have a zero value.
* Flags enums should have plural names. (Dang, this one is pretty nitpicky.)
* ICollection implementations have strongly typed members.
* Identifiers should be cased correctly. (Yes, it actually complains about that, and there were a lot found.)
* Identifiers should have correct suffix.
* Identifiers should not have incorrect suffix.
* Identifiers should not match keywords. (Alias, Object, Event, and Exit classes.)
* Implement standard exception constructors.
* Interface methods should be callable by child types.
* Lists are strongly typed.
* Mark all non-serializable fields.
* Mark assemblies with assembly version (Been doing this, but missed one.)
* Mark ISerializable types with serializable. (Fixed these immediately. Duh.)
* Mark members as static. (It’s not the right solution for the ones FxCop found, but there are problems with what it found.)
* Nested types should not be visible.
* Non-constant fields should not be visible. (Encapsulation again.)
* Operations should not overflow.
* Operator overloads have named alternatives.
* Override equals and operator equals on value types.
* Provide correct arguments to formatting methods.
* Remove empty finalizers.
* Remove unused locals.
* Rethrow to preserve stack details.
* Review visible event handlers.
* Static holder types should not have constructors.
* Test for empty strings using string length.
* Type names should not match namespaces.
* Types that own disposable fields should be disposable.
* Use properties where appropriate.
* Validate arguments of public methods. (Note that FxCop does not appear to be Contract-aware, so some of these will be non-issues.)

Non-applicable issues found:
* Assemblies should declare minimum security.
* Assemblies should have valid strong names.
* Mark assemblies with CLSCompliant.
* Mark assemblies with ComVisible.
* Specify CultureInfo. (This is not an internationalized application.)
* Specifiy IFormatProvider. (Yet again, not an internationalized application.)
* Specify MessageBoxOptions. (This refers to right-to-left reading language support, also not applicable.)

Issues I don’t agree with:
* Do not catch general exception types. (Sometimes it really is the simplest and best solution.)
* Do not declare read only mutable reference types.
* Do not expose generic lists.
* Do not pass literals as localized parameters. Use a resource table instead.
* Identifiers should be spelled correctly. (FxCop didn’t like my use of “x” and “y” as variables in a coordinate class.)
* Identifiers should not contain underscores. (There are a ton of these, about 30% of the Cop’s finds. Pretty much all of our flags are named using underscores.)
* Long acronyms should be Pascal-cased. (Side effects of the previous issue.)
* Only FlagsAttribute enums should have plural names. (Stop whining about names already!)
* Prefer jagged arrays over multidimensional. (No. There’s a specific reason for multidimensional arrays.)
* Short acronyms should be uppercase.
* Used preferred terms.

So yes, there are quite a few things to be fixed. I’m not going to spend any extra effort on that right now — some of these problems will resolve themselves as part of the in-progress changes. Even so, it’s nice to be aware of what doesn’t match preferred style, even if it accomplishes nothing other than having a solid knowledge of which rules are being broken on purpose. I’m sure I’ll post updates on FxCop stats as the code evolves.

Halfway Through Encapsulation

You have passed the halfway point and are nearing your next codebase.

There’s a lot to do, but I’m halfway through encapsulating all of the data for the zone classes. This will give us the power to validate data before assigning it to a variable and will help us reduce the number of boundary checks in the code by moving them to the property we’re trying to set. End result: code that’s easier to maintain and modify.

Visual Studio Refactoring And Encapsulation

I love the refactoring support in MS Visual Studio. It makes certain things like field encapsulation incredibly easy.

For instance, thanks to its origins in C, most of the Basternae 3 codebase doesn’t have encapsulation yet. This means that there are tons of class member variables declared like this:

public string _keyword;

Setting the _keyword member variable to private and creating a property named Keyword with getters and setters that reference the _keyword variable would take about 30 seconds.

With Visual Studio it’s easier: Just right-click on the variable and select “Encapsulate Field”. It will come up with a reasonable property name and automatically generate the code and set the variable to private.

Pretty nice, but nothing to write home about.

But, here’s the magic:

All references to that variable in code are AUTOMATICALLY changed to refer to the property. If that member variable was used in 50 different places, Visual Studio just saved you the trouble of making 50 different changes or doing a search-and-replace that may or may not get everything on the first try.

Of course, this doesn’t automatically update any XML files that have been saved using the old variable name. To take care of that you can do one of two things.

1. Do a search and replace in every XML file that your class would have been serialized to and hope you didn’t miss one.
2. Use the XmlElementAttribute on your property to map the saved attributes to your new type:
[XmlElement(“_keyword”)]
public string Keyword
{

#2 is obviously safer and easier, especially since it doesn’t require changes to existing data. Of course, your data files might be clearer to read if they used the exact property names, but do you want to go through the trouble? Likely not.

No Null Checks

After running the automated tests generated by Pex, it’s amazing how many functions in the old codebase received various class or structure arguments and immediately started working with the data in them without ever checking for null. It was a paradigm followed by the old public code release of Diku, Envy, Merc, etc. and was unthinkingly carried on by the Basternae 2 programmers, myself included. This lack of data validation is being corrected.

It’s no surprise that the old codebase crashed a lot. After seeing the extent of the damage, I feel like I need to go back and revisit the Magma codebase and add a lot of stabilization.

In fact, one of the main things with Basternae 3 that will help stability is the fact that all player-entered commands are executed within a try-catch block. This means that typing in a broken or unsupported command should never crash the MUD, which was a huge problem in the “bad old days”. Instead it will log an error and appear to do absolutely nothing from the player’s viewpoint.