In order to make Managed Extensibility Framework (MEF) a part of your Windows Azure project in Visual Studio 2010 while having a Test Project to test your code there is a nasty reference issue you have to resolve. I posted all the steps to resolving this issue in my recent post MEF + Azure + Visual Studio 2010 = Tricky but doable. but I forgot one step! Here is the final piece of the puzzle. The remaining problem Following the steps in my previous post (link above) you are good to go with your project in all respects...

Putting Managed Extensibility Framework (MEF) in your Windows Azure Application while trying to test your code using Visual Studio 2010 does not work OOTB. It is quite easy to modify – in this case MEF – to enable this scenario. The same issue might result from using other libraries as well. Now that Visual Studio 2010 is out you really do not want to remain on the old version. Sometimes there can be issues working with applications that need to support previous versions of .NET Framework – previous to .NET 4.0 that is. Here is one such issue and...

Here it is the definite resource: New Features in .NET Framework 4 and Visual Studio 2010, (Beta 2). That is if you have 8 hours to kill. Might certainly be worth the time. I’m looking forward to it. Cheers, Magnus Technorati Tags: Microsoft,Visual Studio,IDE,.NET Framework

Need I say more? http://brad_abrams.members.winisp.net/Projects/PDC2008/DotNet4Poster/DotNetFramework4PosterDeepZoom.htm Brad Abrams put it out there for us! Cheers, M. Technorati Tags: .NET Framework,PDC08This work is licensed under a Creative Commons Attribution Share Alike license.

You should make sure the sender and event arguments use a good standard when you raise an event! Use the correct sender and supply good event arguments. I just got stumped the other day about the sender of an event from a third party control. Doesn’t matter what control. What does matter is the fact that I had to dig around unnecessarily long to figure out how the event parameters worked since they did not work as expected. The control I used encapsulated a text label, a textbox and a collection of buttons. The control...

I will show a good way to code for Equality in types and I will point to some nasty pitfalls and things that may go wrong! This topic keeps coming up and today it did again in my company. It’s a classic and so many things while implementing this can go really pear shaped! Some things are as equal as two nuts. Other things are only as equal as two nuts. ;~) Note: Almost two years ago I blogged about the advantages of using IEquatable<T> when overriding .Equals(): Be careful when you override Equals (and...