MPOS Package failed to deploy – Windows cannot install package because this package depends on a framework that could not be found

So recently I successfully build my Retail SDK and uploaded the installer to one of my D365FO environment, but when trying to install the package faced the below issue.

“Windows cannot install package because this package depends on a framework that could not be found”

Here is an extract of the MPOS installation error logs.

System.IO.IOException: Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation.

Windows cannot install package xxx because this package depends on a framework that could not be found. Provide the framework “Microsoft.NET.CoreRuntime.1.0” published by “CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US”, with neutral or x64 processor architecture and minimum version 1.0.23819.0, along with this package to install

The solution was to run run msbuild on a Windows 10 machine instead of building it on my Dev machine (which was on Windows Server 2012 R2) on which I usually build it. (This was based on Microsoft suggestion on a support ticket I logged)

I must say I am surprised since this issue was intermittent for me. Hope this helps.

 

<Update>

As per below extract from Retail handbook, building from Windows Server 2012 should not be an issue. So not sure why I got different results, if you have faced above issue I would be glad to know if you could share more.

For ModernPOS debugging/installation (universal app) either Windows 10 or Windows Server 2016 is required
Note: For a limited time, LCS-hosted development topologies will continue to use Windows Server 2012 R2. What that means is that ModernPOS universal app cannot be installed or run in the debugger on these machines. However, it can be built correctly. Alternatives for ModernPOS development are:
o A separate Windows 10 development machine
o A downloadable Windows Server 2016 based VM from LCS.

</Update>

<Final Update 18 Apr 2018>

The solution is to build the package with configuration=release,

thanks to MVP Kurt Hatlevik  

</Final Update>

 

-Hitesh Manglani

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s