New Version of the Azure Active Directory Module and PowerShell 2.0

Question

Since the last upgrade of the Azure Active Directory Module for Windows PowerShell (64-bit version), we are no longer able to load it in an application targeting .NET Framework 3.5 SP1. The error message that we receive is:
Could not load file or assembly 'file:///C:\Windows\system32\WindowsPowerShell\v1.0\Modules\MSOnline\Microsoft.Online.Administration.Automation.PSModule.dll' or one of its dependencies. This assembly is built by a runtime newer
than the currently loaded runtime and cannot be loaded.
Our application loads and uses the Azure AD PowerShell Module for Azure AD management. The previous version of the module available until September worked well, however, we cannot use the new version because it is built using the .NET Framework 4.0 runtime,
and our application targets .NET Framework 3.5 SP1.
The link for the old version of the module was removed, and since the EULA for the module restricts us from making the old version available on our web site, we need a solution that would enable us
to load the module in our application because we cannot retarget the application to a newer Framework version. In particular,
we need a link that our customers can use to download the old version of the module.
Is there a URL to the old version of the Azure Active Directory Module that we can download the old version from? Can someone help?

Answer 1

Hi Vladimir,
Since I'm not familiar with AZure AD, to get the old version of Azure AD Module, I also recommend you can post in Azure AD forum for more effective support:
http://social.msdn.microsoft.com/forums/azure/en-US/home?forum=WindowsAzureAD
However, for the error you posted, as you said, this is related to .NET version.
I found a similar error, which was solved by upgrading the Powershell version 3.0 on Server 2008 R2 sp1, which also need to update the .NET version on server.
Active Directory Single sign-on Office 365 Powershell Error
If there is anything else regarding the powershell, please feel free to post back.
Best Regards,
Anna Wang
Anna, yep upgrading to version 3.0 simple solve the issue. But WMF 3.0 is not compatible with few things like
SharePoint 2010, Exchange 2007 , SCCM etc.
WMF 3.0 has the same .NET version so how about making a configuration file in version 2.0
I am not really sure if Azure support this but its worth to make your configuration file to support .NET 4.0
$PShome\PowerShell_ISE.CONFIG and $PSHOME\PowerShell.exe.config will be not existing.
So you can make an entry in configuration to support .NET framework 4.0
like shown below
$config_text = @"
<?xml version="1.0"?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0.30319"/>
<supportedRuntime version="v2.0.50727"/>
</startup>
</configuration>
$config_text| Out-File $pshome\powershell.exe.config
$config_text| Out-File $pshome\powershell_ise.exe.config
Close PowerShell Console and open as administrator.
Try loading the modules back and let me know.
Regards Chen V [MCTS SharePoint 2010]