If you choose Self Contained and Windows X86, the problem always happens.
The only case for now, the publish works is if you choose portable. In all other cases, fails to compile.
Part of the error is:
'Start.OnInitialized()': no suitable method found to override
Steps to Reproduce
Follow the steps to create a wpf project and use the component.
Then create a razor file.
Then use option to do code behind.
In the code behind, override OnInitialized.
Then when you publish, publish to folder.
Then choose more options
Then choose Self Contained
Choose x86 for target runtime.
Then publish.
The problem will always happen.
The only workaround I found is to choose Framework Dependent and choose portable.
This means if the computer being deployed on does not have .net core on their computers then does not work.
Also, for now, requires portable to be chosen.
I hope this problem gets fixed.
The only other workaround is all razor files would have to be in a razor class library which can be an overkill if its only used from wpf.
Description
Here is my repository that duplicates the bug. https://github.com/musictopia2/FailPublishSample
If you choose Self Contained and Windows X86, the problem always happens. The only case for now, the publish works is if you choose portable. In all other cases, fails to compile. Part of the error is: 'Start.OnInitialized()': no suitable method found to override
Steps to Reproduce
Follow the steps to create a wpf project and use the component. Then create a razor file. Then use option to do code behind. In the code behind, override OnInitialized. Then when you publish, publish to folder. Then choose more options Then choose Self Contained Choose x86 for target runtime. Then publish. The problem will always happen.
Link to public reproduction project repository
https://github.com/musictopia2/FailPublishSample
Version with bug
8.0.3
Is this a regression from previous behavior?
No, this is something new
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
Windows WPF
Did you find any workaround?
The only workaround I found is to choose Framework Dependent and choose portable. This means if the computer being deployed on does not have .net core on their computers then does not work. Also, for now, requires portable to be chosen. I hope this problem gets fixed. The only other workaround is all razor files would have to be in a razor class library which can be an overkill if its only used from wpf.
Relevant log output