Entity Framework 6 and Vault

[btd]

Hi:

We are on version 7.1 of Vault.
Vault is not playing nicely with Entity Framework 6. When I modify my edmx, vault does not automatically check out the dependent files.
Do you have a fix for this?

btd

[Beth]

Are the files on disk set to read-only before you start editing? If the files are already writable, then an auto-check out can't occur.

I'm assuming that you are making use of the Entity Framework through Visual Studio. If that's not the case, then what IDE are you using?

If you are in Visual Studio, do the files associated with the Entity Framework have locks next to them?

How were the files associated with the Entity Framework added to Vault? By that I mean were they added using Visual Studio, or were they added using the Vault GUI client?

NOTE: This user is also using NuGet per this post here: http://support.sourcegear.com/viewtopic ... 158#p75158.

[btd]

FYI

All the issues seem to be specific to using the Visual Studio Enhanced client. When I unbound my solution and re-bound it using the classic client, everything seems to be working properly. Even the nightly session timeout.

[Beth]

Thanks for the update. I've logged a bug.

F: 17656

[bmcdonald]

Hi, we are experiencing the same problems. We are currently using Vault 7.1 and EF 6. Beth, you mention that you logged a bug. Has this been resolved? Will upgrading our server and clients to 8.0.1 fix this issue?

Thanks.

[bmcdonald]

We are having the same issue. Vault Standard 7.1 and Entity Framework 6. Has this bug been fixed in release 8.0.1?

[Beth]

This issue hasn't been fixed yet. I will make a note on it that more users are running into this.

[bmcdonald]

Beth:

Thank you for the reply. Is there a better workaround for this issue in the meantime?

Brian

[Beth]

You would need to manually check out the packages file and possibly the web.config, or you can switch to the Vault Classic Client. The Classic Client works well with it.