I’ve moved our issue tracking system from FogBugz to Google Code.  You can see the issue tracker here:

http://code.google.com/p/idealbbnet/issues/list

I really like Google Code’s issue tracker and it is of course free to use.  I’m probably going to move the Wiki over as well and then maybe some day in the near future the code too.   I’ve been having a lot of thoughts about open sourcing Ideal BB.NET so if and when I bite the bullet and do it, it will go into this project.

Here is a teaser image from the rating system:

Development has been going really well on this feature.  I was able to utilize a lot of the Asp.Net AJAX toolkit to make this feature work.  I’ve got it doing the actual ratings, but I haven’t written the code yet to filter based on ratings.  That is going to be the hardest part of writing this particular feature.  At the speed that development is currently going, I could see this feature being done by early next week.  I have a few other features that I want to write before doing the 3.1.8 release, but expect the release to go out the door in the next month.

Now that Ideal BB.NET 3.1.7 is out, I thought it would be a good time to upgrade to Visual Studio 2008.  I haven’t had a chance yet to go through the new .NET framework 3.5 to see what benifits (if any) that it would have on Ideal BB.NET, but Visual Studio 2008 lets you target .NET 2.0 apps so I figured upgrading wouldn’t hurt me.  I was correct.  The upgrade went smoothly and everything seems to work fine. 

I’m still wanting to go through the code and upgrade a lot of the code to .NET 2.0 features, like using Generics instead of ArrayLists, etc..  But that stuff is going to have to wait until I finish some of those new features we’ve got planned.

As far as Visual Studio goes, the new develpment environment has a couple of interesting features including some nice SQL tools for doing schema comparisons and generating change scripts.  It could be useful.

I’ve been searching for a really easy way to automate putting together builds of Ideal BB.NET.  Putting together a build usually takes about a day to do and has a lot of small steps.  For example:

1. Do a clean release build in visual studio
2. Copy the files to a new directory
3. Clean out the web.config files
4. Remove read-only on the files
5. Remove custom avatars and uploaded files
6. Run codeveil on the DLL’s to obfuscate them
7. Create directories for each of the builds CORP, LITE, etc..
8. Run SQL DIFF on the new database and create upgrade scripts
9. Zip up each release folder
10. Copy the files up to the web server.

Using Visual Build Professional, I’ve automated almost all of this so that I can press a button, relax with a cup of coffee and watch everything automatically put together.   Its really easy to use and works very well.  Visual Build Professional.

I probably wrote over 1000 lines of code over the past few weeks preparing for the release of Ideal BB.NET 3.1.7.  This build is mostly a bug fix build, but it also adds a new licensing system which will not only make it easier for us to license the product, but make it a lot easier for you to install and upgrade the product.

With the 3.1.7 release will be a new version of the Ideal Science web site which will allow you to manage your serial numbers and maintainence contracts. 

Lastly, the 3.1.7 release is going to be ready for some big new featues that we’ve got planned.  Which features get implemented first depends on the answers we get from the recently published questionaire.  I’m hoping the reply by email wins, because that is a feature that I’m excited about creating.  I’ve got some great ideas for it.