Method not found: 'Boolean Csla.Validation.CommonRules.MaxValueNullableDecimal

Method not found: 'Boolean Csla.Validation.CommonRules.MaxValueNullableDecimal

Old forum URL:

cqncsla posted on Tuesday, November 16, 2010


I'm having an error message 'Method not found: 'Boolean Csla.Validation.CommonRules.MaxValueNullableDecimal'. It only happens to some users but not others. This is not the new codes and all users didn't have this error before. I can't debug since it never happens to me. Does anyone have any idea?

bniemyjski replied on Tuesday, November 16, 2010


Can you please post the full stack trace. Also do you have different screens based on authorization levels? Can you narrow down to what users are experiencing this error and see if their is a pattern.


-Blake Niemyjski

cqncsla replied on Wednesday, November 17, 2010

Stack trace:

System.MissingMethodException: Method not found: 'Boolean Csla.Validation.CommonRules.MaxValueNullableDecimal(System.Object, Csla.Validation.RuleArgs)'.
   at Library.NewLoan.AddBusinessRules()
   at Csla.Core.BusinessBase..ctor()
   at Csla.BusinessBase`1..ctor()

I use ClickOnce to deploy the app to IIS server. I found out that the CSLA.dll on the client machine is not updated with the CSLA.dll in the deployment website. However it just happened to some users recently. If I manually update the CSLA.dll on the user machine, it solves the problem.

My question is now about the ClickOnce. My last version of CSLA.dll was built on 4/7/2010 and deployed to the server. When CSLA.dll is downloaded to user machine via ClickOnce, it shows the date of the installation date. In this case, it works.

The weird thing is on the machine that CSLA.dll is not updated. Even if the app is uninstalled, the CSLA.dll is removed from the user machine. Then a new install again downloads the OLD CSLA.dll. I don't know how the old one keeps being downloaded to that machine.

Do you have any idea?

JonnyBee replied on Wednesday, November 17, 2010


Does the Csla assemblies have the same version number and file version number?

That could "fool" the click once installer to think that the correct assembly is already installed.

cqncsla replied on Friday, November 19, 2010

The Csla have the same version number and file version number.

My solution was to remove Csla reference and add it back before publishing. That forced the ClickOnce to update the assembly on user machine with the one on the server.

Thanks for your all participation.

Copyright (c) Marimer LLC