Bug #50895 Support for .NET 4.0

Description:
This came via private email from an MS employee:

> MySQL is used by many web applications and we worked with Robin/Adam 
> last year to include it in the Microsoft Web Platform Installer. .NET 
> applications communicate with MySQL via the ADO.NET driver for MySQL.
> The MySQL .NET Connector installs a number of assemblies and registers 
> a provider factory in 
> %windir%\Microsoft.NET\Framework\v2.0.50727\Config\machine.config as
> follows:
> 
> <system.data>
> 
>                                 <DbProviderFactories>
> 
>                                                 <add name="MySQL Data 
> Provider" invariant="MySql.Data.MySqlClient" description=".Net 
> Framework Data Provider for MySQL"
> type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data, 
> Version=5.2.5.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d" />
> 
> </DbProviderFactories>
> 
>                 </system.data>
> 
>  
> 
> As we are very close to shipping the .NET Framework V4.0, the MySQL 
> connector needs to add the same registration in the .NET 4 
> machine.config located in 
> %windir%\Microsoft.NET\Framework\v4.0.30109\Config\machine.config. The 
> MySQL .NET Connector MSI will need to detect if both versions of the 
> .NET Framework are present and would need to register itself in both.
> 
>  
> 
> With who can we work to ensure that the MySQL experience is not broken 
> once the .NET Framework V4.0 releases?
> 
>  
> 
> It would be great if you could pass this to someone in charge of MySql 
> Windows installer.

How to repeat:
?

Verified by looking into code.

Closing this as a bug because we have this listed as a feature of our upcoming 6.3.  We will be supporting .NET 4.0 and VS 2010 in 6.3