New Posts New Posts RSS Feed: Post-build Event Command Line
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Post-build Event Command Line
 Post Reply Post Reply
Author
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
danielp37 View Drop Down
Newbie
Newbie


Joined: 18-Mar-2008
Location: United States
Posts: 29 		Post Options Post Options   Quote danielp37 Quote  Post ReplyReply Direct Link To This Post Topic: Post-build Event Command Line
    Posted: 05-Jun-2008 at 1:04pm
I noticed that the command lines for copying the CSDL, MSL, SSDL and ADO.NET assembly to the TargetDir of the project that references the DevForce EF project have hard-coded paths to these files rather than using some of the Macros.  This will cause problems in a multi-user environment where the source may not be in the same location on all developers drives.  Has this been fixed in the beta2?

For example, here are the first couple of lines in the post-build event:

rem [IdeaBlade-begin]
copy  "C:\Data\src.DevForce\HEServerModel\bin\Debug\*.csdl" "$(TargetDir)"

Thanks,

Dan
Back to Top
kimj View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 09-May-2007
Posts: 1391 		Post Options Post Options   Quote kimj Quote  Post ReplyReply Direct Link To This Post Posted: 06-Jun-2008 at 10:47am
The command line for the post-build event is regenerated with every build of the project, so there shouldn't be a problem in multi-user environments, after the first build.
 
We have made some changes to this in Beta2: 
  1. You can optionally disable the post-build command generation via an option in the Object Mapper.
  2. Generation of the command line is now done at the beginning of the build rather than following a successful build, to eliminate the need to build twice to get a correct command line.
  3. Improved error handling within the batch.
  4. Support for embedded resource files (we won't try to copy them to the target directory).
  5. A tweak to project dependencies to make the server model project a dependency (but not a referenced assembly), to ensure that it will be rebuilt when necessary.
 I'm not sure why we didn't make more use of macros in the command line.
Back to Top
danielp37 View Drop Down
Newbie
Newbie


Joined: 18-Mar-2008
Location: United States
Posts: 29 		Post Options Post Options   Quote danielp37 Quote  Post ReplyReply Direct Link To This Post Posted: 10-Jun-2008 at 8:51am
The only problem I see with the post-build event being regenerated with every build is if the project is in source control, it can potentially cause a bunch of unnecessary changes if the multiple users have their source in different locations on their hard drives.  I suppose this could be worked around by disabling the post-build command generation and manually crafting the post-build event to be agnostic to the location on the hard drive or to use relative paths.

Would turning off this option be a per-user setting or would it be part of the settings for the project or solution so that once it was set, we wouldn't have to change the setting on each of the other developer's computers?

Thanks,

Dan
Back to Top
kimj View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 09-May-2007
Posts: 1391 		Post Options Post Options   Quote kimj Quote  Post ReplyReply Direct Link To This Post Posted: 10-Jun-2008 at 10:33am
The option in DevForce EF Beta2 to turn off the post-build command generation is set for the domain model, and is saved to the *.ibedmx file.

Edited by kimj - 10-Jun-2008 at 10:34am
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down