Skip to content
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

warning PRI263: 0xdef01051 #794

Closed
SachinPNikam opened this issue Nov 6, 2017 · 4 comments
Closed

warning PRI263: 0xdef01051 #794

SachinPNikam opened this issue Nov 6, 2017 · 4 comments
Labels

Comments

@SachinPNikam
Copy link

@SachinPNikam SachinPNikam commented Nov 6, 2017

I am getting the warning PRI263: 0xdef01051 after added the csla core in uwp project

eg:
3>GENERATEPROJECTPRIFILE : warning PRI263: 0xdef01051 - No default or neutral resource given for 'Csla.Properties.Resources/FailedOnServer'. The application may throw an exception for certain user configurations when retrieving the resources.

@rockfordlhotka rockfordlhotka added this to the 4.7.100 milestone Dec 14, 2017
@rockfordlhotka rockfordlhotka self-assigned this Dec 14, 2017
@rockfordlhotka
Copy link
Member

@rockfordlhotka rockfordlhotka commented Dec 14, 2017

Just to clarify, this is in CSLA 4.6, not the 4.7 prerelease?

@rockfordlhotka
Copy link
Member

@rockfordlhotka rockfordlhotka commented Feb 23, 2018

A further note on this. It appears that the problem exists when using the old style csproj file for UWP and is related to this thread:
https://developercommunity.visualstudio.com/content/problem/82838/uwp-resource-handling-fails-when-baseintermediateo.html

One workaround suggested by Microsoft is to remove the baseintermediateoutputpath element.

Another workaround is to update the project to use the more modern csproj format.

@rockfordlhotka
Copy link
Member

@rockfordlhotka rockfordlhotka commented Mar 15, 2018

This remains an issue 😢

And, because these are warnings, I'm not going to hold up the 4.7.100 release to resolve it, as I haven't found a direct/simple resolution.

@rockfordlhotka
Copy link
Member

@rockfordlhotka rockfordlhotka commented Apr 19, 2018

@SachinPNikam did you close this because the problem no longer exists? I was encountering the issue and to my knowledge it still is a problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.