QuoteReplyTopic: When saving files in the Object Mapper, all of the xxxDataRow.cs files are removed and added back in Posted: 12-Jul-2007 at 11:25am
We notice that each time we choose the Save option in the Object Mapper, all of the xxxDataRow.cs files are removed and added back in. In many cases, we may have only renamed a relationship, added a column, etc. Why are all of the classes removed and readded if they are not changed? We notice that when we then exit the Object Mapper, that Visual Studio is then hammering the processor on our local machine as it rebuilds the Intellisense for all of the objects that were just readed. We now have 275 business entities and project to have close to 1,000 by the end of the year. We are concerned about our developer productivity. Is it really necessary to remove and re-add entities that are not changed? I can see it being a requirement the first time moving to a new release – but not every time.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum