http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660I think Microsoft went on a shiny but wrong way with this designers. Even the LINQ designer suffer conceptually the same problem. What is so hard to have an addin that shows you all the relations visually, but you specify the relations using attributes directly in code? I wrote myself a tiny orm that is based solely on attributes, and i use an addin to visualize and manage relations. I use a searchable treeview for showing that information, no big graphs that layout silly automatically. I do not have any problems with Source Control. Why cannot Microsoft think simple? http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment8http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment8Sat, 24 May 2008 07:21:14 GMTPeter, Consider an application that is in production, but is under continuous development. If you find a bug in production, you can't apply the changeset to the trunk. Feature branches are impossible, etc. This is critical issue http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment7http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment7Thu, 22 May 2008 17:06:24 GMTI'm more inclined to agree actually. I prefer a single user changing the "structure" of the model at once, but that many people can edit the individual classes to add method implementation etc. I see the model as a single conceptual "thing" that should be modified in its entirety. http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment6http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment6Thu, 22 May 2008 13:24:19 GMTAt this moment I see these way for solving such problems 1) You are somehow modifiing source control program, i.e. its client part for autoresolving such conflicts 2) You can write some code in your dsl package, which can save/load parts of dsl from multiplefiles. What I know - ActiveWrtier plugin for Castle ActiveRecord generates hbm mappings for each class in different files. So you have to write dsl package, which will save it's information in different files in any source control -friendly format and which will load that information on loading. http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment5http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment5Wed, 21 May 2008 11:36:14 GMTSpeaking completely off the cuff now, I don't think it is possible with the EF. I _think_ that the underlying framework supports this, but the UI doesn't. You are better off asking an EF expert. http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment4http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment4Tue, 20 May 2008 15:31:21 GMTOren, I cannot try it. Could you please tell if it is possible with EF to have many packages of the same model (eg: design Security, Payments, Accounts etc on different surfaces). If there is no anything like that than EF is just a child-play for demo projects. http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment3http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment3Tue, 20 May 2008 09:20:12 GMTI guess there is no option to have each class in a separate xml file? http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment2http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment2Mon, 19 May 2008 20:20:46 GMTMicrosoft still believes in exclusive checkout model for source control. http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment1http://ayende.com/3322/reviewing-the-entity-framework-source-control-support#comment1Mon, 19 May 2008 18:58:46 GMT