This has caught me out a couple of times now. I was getting this exception:
Castle.MicroKernel.ComponentActivator.ComponentActivatorException: ComponentActivator: could not instantiate MyNameSpace.ClassName ---> System.ArgumentNullException: Value cannot be null.
Parameter name: types
at System.Type.GetConstructor(BindingFlags bindingAttr, Binder binder, Type types, ParameterModifier modifiers)
at Castle.MicroKernel.ComponentActivator.DefaultComponentActivator.FastCreateInstance(Type implType, Object arguments, Type s
The exception could be a bit more informative - it turns out this is caused by not providing a public constructor on the class (it was accidentally set to ‘protected’).
I went to renew our RAA membership this morning. The paper bill said we owe $170.
I went to the web site to pay online, but was greeted by this:
TOTAL (including GST) $170.01
Yes, they’re overcharging me by 1c.
I rang them up to let them know (and also paid the correct amount while I was at it).
Could this be salami slicing, or more likely someone’s made a silly rounding error. Can’t those IT people ever get it right?
“I’m sure there was a tree around here last time”
So exactly how much faster are the latest hard disks? A number of people commented that using the old IDE disk on my Dad’s new Vista 64bit box wasn’t the best idea. I grabbed a copy of HD Tune to get some benchmarks of each of the 4 disks in the system to get an idea of how the drives compared.
Here’s what I found:
||IDE Disk 1
||IDE Disk 2
|Transfer Rate Minimum (MB/sec)
|Transfer Rate Maximum (MB/sec)
|Transfer Rate Average (MB/sec)
|Access Time (ms)
|Burst Rate (MB/sec)
So that 1Tb drive really is quite a bit faster than the other drives after all.
I’ve since re-configured the new Vista box to use the fast drive for the operating system, and left the other drives in for video files (but with the knowledge that it will be a simple upgrade path to swap them out for additional SATA drives as required).
Microsoft Code Analysis Tool .NET is a new tool to detect certain vulnerabilities in your code – including Cross Site Scripting, SQL Injection, Process Command Injection, File Canonicalization, Exception Information, LDAP Injection, XPATH Injection and Redirection to User Controlled Site.
Also there’s a beta release of version 3 of the AntiXSS library which can help reduce the chance of cross-site scripting vulnerabilities in your ASP.NET application.