July 2004 - Posts
My friend Didier got some nice pictures about sun flowers he got from France-Anne :-) Nice with those rainy days :-(
It is about ways to change your coding so that your code is more testable but it is also a good reminder about good design. I really liked the article, nice work Justin.
- Use Interfaces
- Define a base test class
- As much as feasible, make everything return a value
- Separate data access from business logic
- Make use of configuration
- Make Your Classes Do Only One Thing
- Have Domain Object Factories
- Think carefully about packaging, assemblies and namespaces
- Pick a logging strategy early
Did I miss one or it is just 9 and not 10 like in the title of the article: 10 Ways to Make Your Code More Testable.
After beta testing Groove 3.0 for a certain time on a Virtual PC with non productive data and after it final release of yesterday, I decide to upgrade. I have two computer and on each I have two differents Groove account. On my server the update worked perfectly but on my notebook I have issues with one of my account that doesn't update. I am waiting feedback from the support of Groove to solve my issue. And for sure it is with my business account. They will fix it for sure. Be positive.
In another area I installed Firefox and Thunderbird. I am using Thunderbird only to acces newsgroups, but I am really convinced about it, and it will certainly replace outlook express, after some more test. Concerning Firefox, it is really cool, and I jumped from Maxthon (new name for MyIE2) to it and uninstalled Maxthon and MyIE2. I am happy that my site Tech Head Brothers renders right on it.
After importing the database to my development server, use sp_change_users_login to map an existing user in a database to a Microsoft® SQL Server™ login.
I like the idea of the blog to kep some stuff in mind, or to find them quickly.
After uninstalling V2i from Symantec I was asked to reboot my notebook. The reboot took for ever so I decide after 30 minutes to switch it off. Problems started when I rebooted, lots of drivers where missing and it seems that I lost the plug and play features. One of the first driver I decided to recover was the Sound driver. This is the way I recover from that sound driver issue.
- In services, check that WinAudio service is enabled, set to automatic, and running.
- In Device Manager, System Devices check that Plug and Play Software Device Enumerator is installed and running
If not , then you need to reinstall it:
- Copy machine.inf from %windir%\inf to your desktop
- Remove line ExcludeFromSelect=*
- Use Add new hardware wizard using the Have Disk option
- Select the machine.inf you saved on the desktop
- Install Plug and Play Software Device
If the sound card is listed in the device manager, then uninstall it and start a scan for hardware changes. Afer installing it again I got the sound back live.
I did the same for several other drivers that were missing on my notebook. And now it seems to be ok.
More Posts « Previous page