Errors during build

CoronaCards (Corona in native apps) CoronaCards for WP8
#1

Yesterday I started getting the error listed below and I thought it had something to do with trying to add AdMob to my project but the error is on all my projects which previously it was not. Anybody else experiencing this error. I installed update 4 for Visual Studio but it still has the same problem. Also sometimes if I change the version of Corona Cards I get the second error below. 

ERROR 1:

Error 1 Retrieving the COM class factory for component with CLSID {2D0A16C9-53D9-42C1-BCC2-8D2A135E2163} failed due to the following error: 8001010e The application called an interface that was marshalled for a different thread. (Exception from HRESULT: 0x8001010E (RPC_E_WRONG_THREAD)). 0 0

ERROR 2:

Error 1 Exception from HRESULT: 0x89721800 0 0

#2

Does this error happen to you when you are doing a build&run to the WP8 emulator?

If so, it sounds like you’re running into an issue with Microsoft’s WP8 emulator as described here…

   https://social.msdn.microsoft.com/Forums/windowsapps/en-US/796ea925-c1bf-4fb3-bc67-4967823b51eb/exception-from-hresult-0x89721800-when-deploying-windows-phone-in-visual-studio-2012?forum=wptools

Try doing work-around #1 described in the above link to see if that solves the problem for you.

#3

The emulator has never worked for me and it restarts my computer when I try and use it so I have been building to the device which has worked up until yesterday. 

I have tried deleting folder which does not help and I try and uninstalled the WP8 emulator but nothing happens.

I also installed other versions of Visual Studio but the same error occurs with them.

#4

When do the above errors happen?

During a build?  When you run your app?

#5

Never mind about my last question.  Your forum topic header states that this happens during the build.

Well, in this case, this suggests that something is wrong with Visual Studio’s tools like the link I posted up above suggests.  The solution posted by Microsoft recommends that you delete the “%LOCALAPPDATA%\Microsoft\Phone Tools\CoreCon\10.0” folder.  If that doesn’t work, then you have to uninstall Visual Studio and re-install it.  I really don’t know what else to suggest.  Somehow the tools got corrupted.

#6

After re-installing WP8 emulator again it started working again. At this point I am not really sure what fixed it but I glad it is working again. Hopefully that won’t happen again :frowning:

#7

Does this error happen to you when you are doing a build&run to the WP8 emulator?

If so, it sounds like you’re running into an issue with Microsoft’s WP8 emulator as described here…

   https://social.msdn.microsoft.com/Forums/windowsapps/en-US/796ea925-c1bf-4fb3-bc67-4967823b51eb/exception-from-hresult-0x89721800-when-deploying-windows-phone-in-visual-studio-2012?forum=wptools

Try doing work-around #1 described in the above link to see if that solves the problem for you.

#8

The emulator has never worked for me and it restarts my computer when I try and use it so I have been building to the device which has worked up until yesterday. 

I have tried deleting folder which does not help and I try and uninstalled the WP8 emulator but nothing happens.

I also installed other versions of Visual Studio but the same error occurs with them.

#9

When do the above errors happen?

During a build?  When you run your app?

#10

Never mind about my last question.  Your forum topic header states that this happens during the build.

Well, in this case, this suggests that something is wrong with Visual Studio’s tools like the link I posted up above suggests.  The solution posted by Microsoft recommends that you delete the “%LOCALAPPDATA%\Microsoft\Phone Tools\CoreCon\10.0” folder.  If that doesn’t work, then you have to uninstall Visual Studio and re-install it.  I really don’t know what else to suggest.  Somehow the tools got corrupted.

#11

After re-installing WP8 emulator again it started working again. At this point I am not really sure what fixed it but I glad it is working again. Hopefully that won’t happen again :frowning: