-
-
Notifications
You must be signed in to change notification settings - Fork 802
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
MissingManifestResourceException when using 4.6.25-alpha in UAP #274
Comments
I found some potential helpful advice from 2014 when this was discovered to be an issue with WinRT as well. If this sounds like a good solution, then I'm happy to help contribute to the branch targeting UAP/UWP. |
Interesting, thanks for sharing that! I'd suggest a slightly less hacky approach: mark the Resources file for Add a partial class extending the generated one that exposes a How does it sound? On Fri, Jul 22, 2016, 11:52 AM Nick Butcher [email protected]
|
That's a great idea. What branch is the UWP-compatible one so I can target my code at the right place? I've forked the repo and I'll test this idea there. |
netcore should be the right one, yes. Thanks! On Fri, Jul 22, 2016 at 1:12 PM Nick Butcher [email protected]
|
This still seems to be an issue in the latest stable release. Is there any workaround? |
@achocron: Meaning, do you get a |
I was going to take a look at this, but the resource generator doesn't add a I also don't know whether Other options:
I find none of those options very appealing. @corsairmarks, did you by change ever find a solution when you were looking at this issue? |
@stakx I never circled back, sadly. I can offer this additional comment on As a fourth option, would it be possible to work around this by, at build time, copying the . The reason this came up for me is that in order to test UWP assemblies (even libraries), the tests have to run as a UWP app. |
I believe In any case – I believe we’d get the same output running a . If I’ve got some spare time soon, I’ll try a couple variations in my fork of the repo and see what we get and what trade-offs there are. |
@corsairmarks: That would be welcome. I am currently not set up to experiment with Windows Runtime development. I also believe that just changing the file extension won't achieve anything as long as the same build tool processes it. And if processing the resw results in a .pri file getting created, .NET 4.5 & .NET Core likely won't be able to use it since they're missing the I think completely giving up a resources file would be a pity, but perhaps justifiable on the grounds that many messages in the code base are already hardcoded into code. Giving up a resources file however should be a last option if it's the only way to unblock UWP. |
Enabling localization capabilities is always a good goal, in my opinion. |
Closing this due to a lack of activity. Given that Moq doesn't offficially support UWP and even a hacky, reflection-based approach by which ResourceManager is exchanged for a ResourceLoader-based implementation, we'd have to keep all string resources around in double (once as embedded resx, once as a pri file). Not exactly neat, we're probably better off not solving this in a hacky way. |
It appears the
Times.*()
methods use a *.resx file to hold their string resources. That apparently won't work in UAP/UWP.Notably, this breaks doing things like:
A potential solution is moving to using *.resw files instead. I'm not sure how that would affect backwards compatibility.
I have an repo where I can point at code causing this exception when running xUnit tests for a UAP library. Please let me know whether that would be helpful and I'll link it here if so.
The text was updated successfully, but these errors were encountered: