Stumbled across a very strange “issue” with iGoogle. Very easy to reproduce:

Continue reading »

In VB.NET you have always been able to use optional parameters:

Sub Foo(ByVal p1 As String, Optional ByVal p2 As String = "default value")
End Sub

'Call to Foo with 1 of the 2 parameters is allowed
Foo("p1 value")

Now in C# 4.0 we get the same support:

void Foo(string p1, string p2 = "default value")
{
}

//Call to Foo with 1 of the 2 parameters is allowed
Foo("p1 value");

Continue reading »

But I for one, think this is too little too late. Is this enough to make us migrate of off Subversion, NUnit or CruiseControl.NET?  No but it might be able to fill a very small gap left by open source tools.  But I will not be switching from any open source frameworks for Team Foundation Server 2010.  We needed this about 5 years ago, why the U-Turn Microsoft? Probably because of the lack of Team System take up? Come on who do you know that uses MSUnit or Team Foundation Version Control (TFVC)?

Source: http://blogs.msdn.com/buckh/archive/2009/10/20/tfs-2010-server-licensing-it-s-included-in-msdn-subscriptions.aspx

Usually when I need to call a JavaScript function using a string I use:

function myUsefulFunction() { //useful code }
var foo = 'myUsefulFunction();';
eval(foo);

However a more elegant approach would be to use:

function myUsefulFunction() { //useful code }
this['myUsefulFunction']();

Continue reading »

Despite the rumours LINQ to SQL is fully supported in .NET 4.0, it has even been improved including better mockability, link below has more details .  Good news for all the early adopters you don’t have to redevelop all your LINQ to SQL apps to entities, just to be supported by Micro$oft.

http://damieng.com/blog/2009/06/01/linq-to-sql-changes-in-net-40