Devart Forums

I went to the file you specified to modify and the project import node you mentioned already exists in this file. However, in the custom extensions path indicated in the node, there is no file with the name "Devart.Data.Entity.targets".

There is however in the ...\MSBuild\Devart\v4.0 a file named "Devart.Data.Entity.10.targets".

I have tried changing the Custom.After.Microsoft.Common.targets project import node to reference the file with the "10" in the name. If I do this Visual Studio locks up when I open any project with a devart model in it.

I have also tried copying from the v3.5 framework directory the Devart.Data.Entity.targets file and creating the copy in ...\MSBuild\Devart\v4.0 which would then create a valid reference in the Custom.After.Microsoft.Common.targets file. This has the same effect that will lock up Visual Studio.

I know don't claim any official support for the VS2010 RC, but any help is appreciated and perhaps we will be happy to provide any and all valuable feedback as we help test this scenario.

Using the following configuration:

Windows 7 x64 Enterprise Edition
Visual Studio 2010 RC (Not beta 2...)
dotConnect beta (5.55.90 I think is the correct version number - latest build)

Attempting to create a new console application, add a new Devart Model to the project, drop on one table from the database on to the model.

Any EF query generates the following error:

"Unable to load the specified metadata resource."

Have tried:

All of the above with respect to adding the Devart.Data.Entity.targets files to both v3.5 and v4.0 framework directories.

Ensured that the Custom.After......targets file that exists was created in the MSBuild\Devart\v4.0 custom build task directory and included the expected import node.

Attempted to add the import statement to the Microsoft.Common.targets file in the v3.5 and v4.0 directory with only success in the v3.5 directory as I could never get permission to the v4.0 file to make the appropriate changes (Trusted Installer is the only user with permissions to modify this file).

Have attempted to open the model for editing and change the model level property to include in output directory instead of embed as resource, then clean, rebuild and set the property back to embed as resource with no luck. Also, when setting this property to include in output directory, none of the .*sdl files are generated or written to any output directory.

I have also examined the sizes of the .dll output as the original poster in this thread indicated and did notice a significant difference under VS2010 where the dll is smaller (by approximately the size of the respective resources that should be embedded in the dll and do not appear to be).

You have noted that there was a fix for this with a previous release and it appears that it may have resurfaced after a couple of releases, so I am curious what my next steps need to be. Can you describe the details of the fix or do you have any recommendations for running successfully under v4.0 VS2010 RC?

Is there any update on when the Entity Developer tool will be updated with respect to EF4? I am running in to many issues trying to get it to work and am now having to wait until Entity Developer is released to move forward.