-
Notifications
You must be signed in to change notification settings - Fork 965
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warnings on Windows Phone 8 Project #330
Comments
Thanks for reporting this @holymoo. Just wondering: are you using Advertising SDK? |
Thansk for getting back to me @MehdiK |
Those warnings AFAIK are related to Advertising SDK. I thought they would only appear if you had referenced the SDK but I might be wrong. Would you be able to double check that please? |
I am facing the same issue. |
I looked into this issue somewhat, it almost looks like visual studio is freaking out because the resource files are not in the correct format. This isn't the case, but visual studio send to think so. -----Original Message----- I am facing the same issue. |
By installing Humanizer package, currently you get the English resource file as well as resource files for all the other available languages (this behavior will change in v2). Some of the resource files have some resources that don't exist in the English resource file (to deal with dual, paucal numbers etc). Normally, apart from downloading unnecessary files, this is fine; but somehow when you have the Advertising SDK on your machine VS goes berserk and expects all the resource files to have the same resources! This is a known bug in the Advertising SDK and there is nothing Humanizer can do about it. The change in V2 will fix the default/English package with the SDK installed but as soon as you download another resource file with extra resources, you will see the same behavior. |
Can you please try this again on the latest release? We have fixed a whole bunch of issues around these warnings. |
Sure, I can test it out tonight. -----Original Message----- Can you please try this again on the latest release? We have fixed a whole bunch of issues around these warnings. |
When adding this library it generates a great deal of warnings on build.
If you would like, I can publish the project to github to demonstrate this issue.
Here are the warnings:
The text was updated successfully, but these errors were encountered: