New Posts New Posts RSS Feed: Team Foundation Server 2008-ORM issues
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Team Foundation Server 2008-ORM issues
 Post Reply Post Reply
Author
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
jocur View Drop Down
Newbie
Newbie
Avatar

Joined: 26-Jul-2011
Posts: 4 		Post Options Post Options   Quote jocur Quote  Post ReplyReply Direct Link To This Post Topic: Team Foundation Server 2008-ORM issues
    Posted: 26-Jul-2011 at 9:09am
Hi All,

We are a group of developers working with IdeaBlade Classics & Cabana style applications. Many times we are experiecing problems when one developer check ins code when he has made changes to the ORM .

The architects says than we do not need to check in the Model.Orm file, just the Model classes. However when we have checked in that correctly,sometiems the developers checking out the application cannot build it correctly. The developers checking out the code, do not override their ORM.file or IDeaBlade config file, just the Classes and the Model project. Sometimes they get problems and sometimes it works fine.

I was wondering if there is a "best practices guide" on how multiple developers should work with the ORM, and whether is recommended to always update the ORM file(check in always) or indeed we can work with our own ORM' S files and if this does not affect the code been checked in.

Any help on this will be very much appreciated

Regards

Jo
Back to Top
robertg View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 15-Mar-2011
Location: California
Posts: 87 		Post Options Post Options   Quote robertg Quote  Post ReplyReply Direct Link To This Post Posted: 26-Jul-2011 at 10:33am
Jo,
 
We don't have a proper best practices guide, but  you're on the right track with these questions. Since the designer gets its information from the ORM, anyone who's developing with the designer absolutely needs to have the latest/correct version of the ORM. If you have one or more developers not including it in their CRM updates, then you run the risk of unintended consequence and confusion/data-loss in the configuation of your model.
 
The same goes for the configuration file... I understand that it can be a pain to have to update the file to reflect the local settings on a development machine, but as the process of development can often result in changes or additions to files like these, it is very important that every time  a new version is available, it should be retrieved and resolved for differences from your working version. Your developers can get away with not checking in changes to the config, if they know that they've only made changes that effect local settings for their development environment and that the application does not need these changes to set its configuration properly.
 
Yours,
Robert
Back to Top
jocur View Drop Down
Newbie
Newbie
Avatar

Joined: 26-Jul-2011
Posts: 4 		Post Options Post Options   Quote jocur Quote  Post ReplyReply Direct Link To This Post Posted: 26-Jul-2011 at 10:48am
Hi Robert,

Thank you. Your answer has been very helpful.

Regards

Johanna
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down