Ok.. i found the same issue on this threat: http://www.dotnet247.com/247referenc...25/129525.aspx

I used their solution and it works.. now the question is, is this a flaw in the framework? If so, will it be fixed?

Thanks,
-mcd