This is a migrated thread and some comments may be shown as answers.

[Solved] Splitting Configuration Files - Error

2 Answers 61 Views

Design Time (Visual Designer & Tools)

This is a migrated thread and some comments may be shown as answers.

This question is locked. New answers and comments are not allowed.

David Hollins asked on 30 Jul 2010, 07:30 PM

Since my main domain library was becoming too big, I wanted to seperate it into multiple. So I created a new project and created a config file in it and copied a few of the classes from the original assembly to the new assembly and also copied some of the applicable configuration from the original assembly's config file into the new assembly.

Now when I go to bring up the Forward Mapping dialog in the new assembly, I get the error:

Error 126 OpenAccess: System.NullReferenceException: Object reference not set to an instance of an object.
   at OpenAccessRuntime.Relational.metadata.RelationalRefField.SetupInMemoryHandling()
   at OpenAccessRuntime.metadata.FieldMetaData.SetupInMemoryHandling()
   at OpenAccessRuntime.metadata.ClassMetaData.SetupInMemoryHandling()
   at OpenAccessRuntime.metadata.MetaDataBuilder.SetupInMemoryHandling(ClassMetaData[] classes)
   at OpenAccessRuntime.metadata.MetaDataBuilder.buildMetaData(DataObjectsRoot[] roots, Boolean ignoreNoClasses)
   at OpenAccessRuntime.Relational.RelationalMetaDataBuilder.buildMetaData(DataObjectsRoot[] roots, Boolean ignoreNoClasses)
   at OpenAccessRuntime.Relational.RelationalStorageManagerFactory..ctor(StorageManagerFactoryBuilder b)
   at OpenAccessRuntime.storagemanager.StorageManagerFactoryBuilder.createSmfForURL()

If I turn off persistance for the classes I copy into the new assembly and try to remap them it still gives the error and a lot of the data in the Forward Mapping dialog is empty (i.e. table name, column type info, etc.)

Has anyone else receieved this error and if so, is there a way around it?

Thanks in advance!

2 Answers, 1 is accepted

answered on 02 Aug 2010, 07:34 AM

Hi David Hollins,

We are glad to see that you have solved the problem. Such errors might occur in case of insufficient information in the configuration file but it seems in this case it could be something already fixed in the latest version.
Please do not hesitate to contact us if you face any further difficulties.

Best wishes,
Alexander
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items