Devart Forums

We want to have multiple models in a project. Each model should reside in it's on subfolder. We use the Studio Plugin.
If we select Metadata Artifact Processing = "Embed In Output Assembly" then we find the following files in the \obj\Debug folder:
Folder1.Model1.csdl
Folder1.Model1.msl
Folder1.Model1.ssdl

So the correct connection string would be something like this: which is generated correctly in the app.config, too.

With the dbcontext Template and "Save connection string in App.Config" = false the connection string in the context file constructor now is which seems to be wrong (and produces a runtime error because of the missing "Folder1" part). Can you confirm this behavior?

The second question would be: How do we get the "Folder1" part (seems to be the complete folder path to the model in the project) in the dbcontext template? We have to customize the context file generation, because we want to have one single connection string in the App.Config. So we must add the metadata to this string for each context. Our code already works if all models are in the project root.

For better performance the res://*/ should be replaced with the res://MyDefaultNamespace/, is that right?

CopyToOutputDirectory means placing mapping files into the output folder.
EmbedInOutputAssembly means embedding mapping files (.csdl, .ssdl, and .msl) into an output assembly.

wombat wrote:If we select Metadata Artifact Processing = "Embed In Output Assembly" then we find the following files in the \obj\Debug folder:
Folder1.Model1.csdl
Folder1.Model1.msl
Folder1.Model1.ssdl

Looks like the *.csdl, *.msl, *.ssdl files were generated when your model had the MetadataArtifactProcessing="CopyToOutputDirectory" setting.

Assuming that I created the *.edml model in the Folder1 folder in my project, the designed behaviour would be (depending on the MetadataArtifactProcessing value):

1. MetadataArtifactProcessing="CopyToOutputDirectory"
a) connection string b) Folder1.Model1.csdl, Folder1.Model1.msl, Folder1.Model1.ssdl are created in the \bin\Debug folder

2. MetadataArtifactProcessing="EmbedInOutputAssembly"
a) connection string b) there are no Folder1.Model1.csdl, Folder1.Model1.msl, Folder1.Model1.ssdl files in the \bin\Debug folder because they are embedded into application assembly

If you are experiencing a different behaviour, please send us a small test project for reproducing the issue.

Sorry for the delay.

Maybe I gave too much information of our situation and simply mixed up CopyToOutputDirectory & EmbedInOutputAssembly on typing, which has led to confusion. But this is not so important. I would like to cut it down to the second question:

Where do we get the "Folder1" substring from within the DbContext template if Entity Developer generates a connection string which contains
We want to have one "base" connection string without metadata.
We want to customize the code generation to use this base connection string and add the corresponding metadata for each context. We have enough information about the metadata (model name and the string constants) to concat the string except for the path qualifier prefix ("Folder1" below the project root in this case) before the model name:
We fill modelName from the "baseFileName" in the DbContextTemplate.
Where do we get the "Folder1" from?

This would help us a lot. Thank you.

wombat wrote:Where do we get the "Folder1" from?

"Folder1" is a directory where the model is placed in.
Try using the model.FullFileName property which includes the full path to the model file. Does this help in your approach?

Sorry, it does not.

We don't need the full path to the model file, we need the relative path below the project root. We could try to substract the full path to the project from model.FullFileName, but the well known "this.Host.ResolvePath()" does not seem to work: Host is null in the DBContext Template (of course with hostspecific="true"). So we don't get the project path.

How does Entity Developer itself create the realtive path in the metadata in the connection string in app.config?

wombat wrote:We could try to substract the full path to the project from model.FullFileName

Please try this way.

wombat wrote:How does Entity Developer itself create the realtive path in the metadata in the connection string in app.config?

Entity Developer uses Visual Studio's internal variables.

Shalex, don't get me wrong. I appreciate any help I can get.
But as I wrote this in my last post: Where do we get the path to the current project from? I mean...this is a TEMPLATE. We want to use it in different projects. So I don't want to hardcode the path. And the only way I know of is to use

this.Host.ResolvePath

.
https://msdn.microsoft.com/de-de/libra ... 10%29.aspx

This works fine for common T4 files in Visual Studio. Using an Entity Developer T4 file (the DbContext template in this case) "this.host" is null/empty/nothing:

We could try to substract the full path to the project from model.FullFileName, but the well known "this.Host.ResolvePath()" does not seem to work: Host is null in the DBContext Template (of course with hostspecific="true"). So we don't get the project path.

So there is no use in writing "Please try this way." without telling me an alternative or what I'm doing wrong.

wombat wrote:This works fine for common T4 files in Visual Studio. Using an Entity Developer T4 file (the DbContext template in this case) "this.host" is null/empty/nothing.

Devart Entity Model (*.edml) uses a different object model comparing to Microsoft's ADO.NET Entity Data Model (*.edmx).
We will investigate the possibility to support the this.Host.ResolvePath() method in *.edml and notify you about the result.

Please upgrade to the new (5.7.539) build of Entity Developer. Now you can obtain a relative path with the model.GetHostRelativePath() method.