At the time of the Visual Studio and Azure SDK 2.7 releases, Framework 4.6 wasn't supported broadly throughout Azure.This is due in large part to the fact that just as many teams (or more) are responsible for the ongoing development and stability of the Azure platform.If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site. Update (August 14, 2015) - We're happy to announce that . NET Framework 4.6, and many teams across the company have worked together tirelessly to ensure the latest version provides developers a rich ecosystem of tools.Currently, the plan is to roll out the updates to Azure App Service during August 2015.
We take the responsibility for your application's stability seriously and want to communicate that we're taking every precaution to ensure your deployment and hosting experiences will be as rewarding as your development experience.
A little more work is required for applications that make use of Object Context but it still isn’t hard to do.
Here is a checklist of the things you need to do to upgrade an existing application to EF6.
The consequence of this is that applications will need to be rebuilt against the moved types.
This should be straightforward for applications that make use of Db Context as shipped in EF 4.1 and later.