Merging metasource for Telerik doesn't build object

[marketally]

I am a long time user of Telelrik and am grateful that you offer the import and support. I have though found an issue on one of the advanced features I used to use in Telerik which doesn't work. I use the Metadatasource to update my models dynamically in code rather than pushing in from your entity developer because when using containers, I need to distribute my app and have it handle the schema changes dynamically. Telerik excelled in this compared to the other platforms imo, and I accomplished it by like below:

Code: Select all

MetadataSource customdataSource = Telerik.OpenAccess.Metadata.XmlMetadataSource.FromAssemblyResource("mymodel.rlinq");

then I would check and either get the changes or create the database, which works wonderfully.

Code: Select all

            string script = null;
            try
            {
                script = handler.CreateUpdateDDLScript(null);
            }
            catch
            {
                try
                {
                    if (handler.CreateDatabase())
                        script = handler.CreateDDLScript();
                    else
                        return false;
                }
                catch (Exception ex)
                {
                    throw ex;
                }
            }
            if (string.IsNullOrEmpty(script) == false)
                handler.ForceExecuteDDLScript(script);

When I replace the rlinq with the daml, it won't work. I really wish you would offer an export in compliance with the rlinq format for this reason specifically. It is greatly needed especially in scaling containers for unique client installations.

D.

[Shalex]

We will investigate the question and notify you about the result.

[marketally]

Did you also get my question about the foreign keys and .NET Core EF? I sent to support haven't heard back - it is also a blocking issue for me.

[Shalex]

Support for XmlMetadataSource.FromAssemblyResource("MyModel.daml") with the model generated by Entity Developer is on our roadmap. There is no timeframe at the moment.

Did you also get my question about the foreign keys and .NET Core EF? I sent to support haven't heard back - it is also a blocking issue for me.

We have answered you by email.