Barnstokkr
Barnstokkr

Reputation: 3129

Universal App Deploy error code: 2147942411

After porting a Windows Phone 8.0 app into a Universal Windows App I get the compile error

DEP6810 : MdilXapCompile.exe failed with error code 2001.

When building for Release, building for Debug on an emulator works fine.

In the log file I get the message

CrossGen failed

Raw error code: 2147942411

I found that this was asked on msdn, but the answer is not very helpful. They say it's a ERROR_BAD_FORMAT.

Has anyone ran into this issue and found a solution?


Since msdn question asked, I am using Visual Studio 2013 with update 4

Upvotes: 4

Views: 1976

Answers (3)

Benjamin Dykstra
Benjamin Dykstra

Reputation: 1

I was having similar issues (same error). What solved it for me was moving my solution mapping from my local c: drive to my user folder. I'm thinking it was some sort of permissions issue that was being masked by this error.

Upvotes: 0

Barnstokkr
Barnstokkr

Reputation: 3129

The issue was the platform target

When you build for Windows Phone use platform target

Device : ARM

Emulator: x86 or x64

After this issue, I got this issue which I recommend you check out (I don't know if they are linked in some way)


So I ran into this issue again

Working Configuration

I had this settings configuration:

  • Platform: Active(Any CPU)
  • Platform target: ARM

enter image description here

Breaking the configuration

To enable the error message

DEP6810 : MdilXapCompile.exe failed with error code 2001.

just simply change the Platform from Active(Any CPU) to ARM (I expect anything will do)

Now, even if you change the Platform back from ARM to Active(Any CPU) it still gives the error.

Solution

  1. Uninstall the app from the device
  2. Restart the device (and your computer if you feel like it)
  3. Deploy the build again

Hope this helps.

Upvotes: 2

mkabatek
mkabatek

Reputation: 1276

I had the same issue:

Error 1 Error : DEP6810 : MdilXapCompile.exe failed with error code 2001.

changing from release to debug resolved the error. This MSDN post helped me solve it.

Upvotes: 1

Related Questions