warning PRI263: 0xdef01051 #794

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

Comments

Projects
None yet
2 participants
@SachinPNikam

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 the bug label Dec 7, 2017

@rockfordlhotka rockfordlhotka added this to the 4.7.100 milestone Dec 14, 2017

@rockfordlhotka rockfordlhotka self-assigned this Dec 14, 2017

@rockfordlhotka

This comment has been minimized.

Show comment Hide comment
@rockfordlhotka

rockfordlhotka Dec 14, 2017

Owner

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

Owner

rockfordlhotka commented Dec 14, 2017

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

@rockfordlhotka

This comment has been minimized.

Show comment Hide comment
@rockfordlhotka

rockfordlhotka Feb 23, 2018

Owner

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.

Owner

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

This comment has been minimized.

Show comment Hide comment
@rockfordlhotka

rockfordlhotka Mar 15, 2018

Owner

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.

Owner

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 rockfordlhotka modified the milestones: 4.7.100, 4.7.200 Mar 16, 2018

@rockfordlhotka rockfordlhotka referenced this issue in MarimerLLC/cslaforum Mar 22, 2018

Open

CSLA .NET version 4.7.100 release #510

@rockfordlhotka rockfordlhotka removed their assignment Mar 22, 2018

@rockfordlhotka

This comment has been minimized.

Show comment Hide comment
@rockfordlhotka

rockfordlhotka Apr 19, 2018

Owner

@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?

Owner

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