I have a CreateValidator:

        Protected Overrides Function CreateValidator() As IValidator
            Return New ABC.DAL.ValidatorClasses.GeneralTypeValidator()
        End Function

ValidatorClass:

 Public Overrides Sub ValidateEntityBeforeSave(ByVal involvedEntity As IEntityCore)
            Dim toValidate AsGeneralTypeEntity = CType(involvedEntity, GeneralTypeEntity)
            If toValidate.GeneralType = "Abc" Then
                Throw New ORMEntityValidationException("Abc is not valid General Type", toValidate)
            End If
            MyBase.ValidateEntityBeforeSave(involvedEntity)
        End Sub

ButtonClick:

 Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click
        Dim da As New DataAccessAdapter
        Dim entityGeneralType As New GeneralTypeEntity
        entityGeneralType.GeneralType = "Abc"
        Try
            da.SaveEntity(entityGeneralType, True)
        Catch ex As ORMEntityValidationException
            Label1.Text = ex.Message
        End Try
    End Sub

When I click the Button, it throws the exception saying that it was not handled by the User code.

I handled it with Try... Catch and want to display it to the user using a Label.

Am I doing anything wrong?

Please post the complete stack trace and exception exact text

Stack Trace:

 SD.LLBLGen.Pro.ORMSupportClasses.ORMEntityValidationException was unhandled by user code
  Message="Abc is not valid General Type"
  Source="ABC.DAL"
  StackTrace:
       at ABC.DAL.ValidatorClasses.GeneralTypeValidator.ValidateEntityBeforeSave(IEntityCore involvedEntity) in D:\ABCDAL\GeneralTypeValidator.vb:line 19
       at SD.LLBLGen.Pro.ORMSupportClasses.EntityBase2.OnValidateEntityBeforeSave()
       at SD.LLBLGen.Pro.ORMSupportClasses.EntityBase2.CallValidateEntityBeforeSave()
       at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.PersistQueue(List`1 queueToPersist, Boolean insertActions)
       at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.SaveEntity(IEntity2 entityToSave, Boolean refetchAfterSave, IPredicateExpression updateRestriction, Boolean recurse)

After this, the actual error message shows in the Label... Very strange.

It's indeed very strange. What's odd is that the exception type isn't caught by a piece of code which definitely catches that same type.

This is in a webapplication?

Yes Frans. It is a Web Application.

As you told me (in another thread), I have the CreateValidator Class in the same project where the created entities are. And the actual ValidatorClass is in my Web Project.

To test, in a Web Form, I have a button that saves the Entity that throws the exception and it is handled well with Try... Catch.

After the SaveEntity line, it fires to the ValidatorClass' ValidateBeforeSave Method and throws the exception after the "Throw" line immediately.

Most probably there is a version mismatch in ormsupportclasses assemblies in generated code and gui code, as the exception object's type is apparently from another assembly thus not the one in the current appdomain of the webpage

Walaa:

I have three projects:

1st one is the Web Project 2 and 3 are the generated projects of LLBL (Adapter)

I have the created class in the 2nd Project where the entities are.

The Web Project has the ValidatorClass and a form that saves the entity to fire the exception.

In this, what will be the issue? I know I have the build of 17th Oct and it works fine in all other cases.

How do I verify I have the correct version? Can you explain a bit?

Thanks.

Make sure the 3 projects are referencing the same runtimeLibrarys (SD.LLBLGen.Pro.ORMSupportClasses.NETxx.dll), I mean they all are pointing to one physical path.

If the generated code was using the assemblies from the LLBLGen Pro setup folder, and the WebApp is using the a local copy, this might cause the problem -> make them all point to the local copy of the WebApp.

Yes. All are referencing the same physical path of the runtime files.

Another question...

I have defined the CreateValidator in a Partial Class of the EntityClass and placed it in the same project of the created entitites.

In that, I have a line:

Return New <CustomValidator>

When I try to map out the <CustomValidator>, it doesn't recognize (no intellisense) the CustomValidator from the Web Project.

Why?

pandu wrote:

Yes. All are referencing the same physical path of the runtime files.

Could you please rebuild the complete solution and if possible not opt for per-page assemblies? We've had this reported once, however weren't able to reproduce it ourselves, however in a similar way, we ran into this issue ourselves where we changed something in the ormsupport classes to fix a bug, and tried to test it on 2 pages in the same app: we build the webapp and page 1 still showed the bug, page 2 didn't, SAME CODE. Attaching a debugger showed that page 1 used a different ormsupportclasses assembly, very strange.

Another question... I have defined the CreateValidator in a Partial Class of the EntityClass and placed it in the same project of the created entitites.

In that, I have a line:

Return New <CustomValidator>

When I try to map out the <CustomValidator>, it doesn't recognize (no intellisense) the CustomValidator from the Web Project.

Why?

It's a protected method, so it's not visible to code outside the class.