Devart Forums

When I run my msbuild task, I am getting this error:

"C:\_dev\ClassLibrary1\ClassLibrary1\ClassLibrary1.csproj" (Build target) (1) -
>
(DevartEntityDeploy target) ->
C:\Program Files\MSBuild\Devart\v3.5\Devart.Data.Entity.targets(32,5): error
: DevartEntityDeploy: Could not find a part of the path 'C:\_dev\ClassLibrary1\
ClassLibrary1\obj\Release\DataSourceModel1.ssdl'.

0 Warning(s)
1 Error(s)

To test it, create a new project, add a new DevArt Entity model to it, drop one table in from the database. Compile it. All is well.
Now, change the Project Output Directory in the project properties from bin\Debug to bin and from bin\Release to bin.
Now, from a command line, execute msbuild:
C:\WINDOWS\Microsoft.NET\Framework\v3.5\MSBuild.exe /nologo /t:Build /p:Configuration=Release/v:diag
Now, get the error. The changes you guys have made to the DevartEntityDeploy library, seem to have caused it to use a hard coded path to bin\Release. I did not get this error with version 5.35.62.

Thank you for the report.
We are investigating the issue, I will let you know about the results.

Thanks! I look forward to your response because this is preventing me from upgrading.
Perhaps this is irrelevant on my build machine. (It is not a dev machine, it is just used to create builds, not to regenerate the model files.
Can I just rename your MSBUILD library to hide it on that machine?

We have fixed the error. Look forward to the next build.
Thank you for your assistance.

That's great. What about the rest of what I said? Will that work as a temporary stop gap so I can upgrade?

No, it won't.
The issue was associated with the fact that the \obj\Release folder was not found. It is necessary for build process - some temporary files like metadata resources are placed there while the build proceeds. The easiest solution is to create the \obj\Release directory, everything should go smoothly.
The bin folder you specified is intended for the final assemblies, intermediate files will be anyway placed in the obj\Release one.

We have fixed the error, look forward for the nearest build.

Thanks. I got the 146 version today and it has fixed this issue. The build and generation of the pregenerated views is working properly. Thanks for getting this out to us (your customers) so quickly. I am very grateful for Devart's responsiveness.