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

RuleRequiredForAtLeast1Property Error in published Blazor.Server App #1056

Open
huncu16 opened this issue May 9, 2024 · 4 comments
Open
Labels

Comments

@huncu16
Copy link

huncu16 commented May 9, 2024

Hello eXpand Team,

I converted our XAF app from .Net to .Net.Core Framework and create its blazor server app all works fine while starting it from Visual Studio Debug or Relase mode. But if I publish it and start server in IIS or running MyAppName.Blazor.Server.exe i get the following error before login screen display

Error: System.InvalidOperationException: Unable to create a model node for the 'RuleRequiredForAtLeast1Property' rule. The rule type is unregistered. Use the ValidationRulesRegistrator class to register the rule on module setup.

after i get this error
I've be sure about add Xpand.Persistent.Base refence is ok then i've registered it at MyApp.Module.Module.cs in Application_SetupComplate method before initialize it wia code below

ValidationRulesRegistrator.RegisterRule(module.ModuleManager, typeof(RuleRequiredForAtLeast1Property), typeof(RuleBasePropertiesLogic));

but nothing changed in published app. It still works fine in debug or rease started with VS.

I put the screen shots below for callstack

What am i missing?

Clipboard-File-1
Clipboard-File-2

Thanx for answers.

@apobekiaris
Copy link
Member

hard to tell without experementing the most obvious is to blame your publication, so my guess is that RuleRequiredForAtLeast1Property is actually in a different versioned assemby

@huncu16
Copy link
Author

huncu16 commented May 9, 2024

Yes it cannot be publication while relase.exe giving same error and ican build and run in VS. I've checked all versions are same 22.1.302.2

@huncu16
Copy link
Author

huncu16 commented May 17, 2024

Tolis, Hello again,
After been sure all versions are same then I updated my solution from 22.1 to 23.2 (I've planned it after successfull publish in 22.1 but set its plan to early because of this problem) i still get the same error. But there is one diffenrence is now i cannot run my project vi Visual Studio too.

@apobekiaris
Copy link
Member

I am sorry without repro solution cannot help much

@apobekiaris apobekiaris removed their assignment Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants