search

Vungle / Windows-SDK

Other
21 stars 8 forks source link

sdk init crashed in VS 2017 #20

Open vincentely opened 5 years ago

vincentely commented 5 years ago

Vungle SDK 6.3 throws Platform::ClassNotRegisteredException in AdFactory::GetInstance; App crashed. It happened when I upgrade the solution to VS2017 and execute normally in 2015.

gregthatcher commented 5 years ago

Hi Vincentely,

Could you please check your "references". I believe you may have to remove the VungleSDK reference, and then re-add it. Even better, you might consider adding the VungleSDK reference using GitHub. You can find instructions on how to do this at: https://support.vungle.com/hc/en-us/articles/360003059331. Let us know if you need any more help or info.

HUN73R commented 5 years ago

I've encountered a similar issue before and in my case the .NET Native compilation was failing to build the VungleSDK project because our build was looking for a specific version of the .NET Native tools and compiler which were no longer the default in MSVS. An update had upgraded the default toolset and moved older versions to fallback directories and the VungleSDK was silently failing to compile. This then led to us encountering the ClassNotRegisteredException at runtime when trying to create the Vungle instance. I don't know how your project is set up but to fix this issue and get the VungleSDK to compile in to your build again you'll need to do something such as install the appropriate .NET Native compiler NuGet package or point your build process to the correct location of the .NET Native toolset (check out \Program Files (x86)\Microsoft SDKs\UWPNuGetPackages\…)