Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I know you said you don't want to use post build events, but your reason as to why not intrigued me. It sounds like you might be hard coding the name of the .dll in your post build event. That can easily be avoided.</p> <p><code>xcopy "$(TargetDir)*" "c:\common\" /Y</code></p> <p>The <code>*</code> would just cause <em>everything</em> in your bin/Debug/ folder to get copied to your common folder. You could also just copy dlls if you want. Or, if you use <code>$(TargetPath)</code>, you'll copy just the 1 dll that is the result of the project, and not any other related dependencies.</p> <p><strong>UPDATE</strong></p> <p>The way we do it is each projects entire bin folder is copied to a <em>sub</em>folder. Suppose you have 2 projects, <code>WebUtil</code> and <code>HtmlParser</code>, where WebUtil depends on HtmlParser. For both projects, use <code>xcopy "$(TargetDir)*" "c:\common\$(ProjectName)" /Y</code>. This will create c:\common\WebUtil\ and c:\common\HtmlParser. In WebUtil, add a reference to c:\common\HtmlParser\HtmlParser.dll. There will now be 2 copies of HtmlParser.dll in c:\common.</p> <p>c:\common\HtmlParser\HtmlParser.dll // the most recent build. c:\common\WebUtil\HtmlParser // what <em>was</em> the most recent build when WebUtil was built</p> <p>This has all kinds of advantages. If you change the API of HtmlParser, WebUtil will continue to work, since it will have the older HtmlParser.dll until you try to rebuild WebUtil (at which point you'll get build errors because of the changed API).</p> <p>Now, if a 3rd project got in the mix that depended on WebUtil, and you're using some part of WebUtil that exposes classes in HtmlParser, then you'll need to add a reference to <em>both</em> projects from your new project. When you add a reference to HtmlParser.dll, use the one in c:\common\WebUtil. You do this because you're only including it as a necessary requirement of WebUtil. Now you'll always have the version of HtmlParser.dll that matches your current version of WebUtil.dll.</p> <p>I hope that makes sense. It can definitely be a tricky thing to manage. Just wait till you have to start pulling down all your dependencies using svn:externals =P</p>
    singulars
    1. This table or related slice is empty.
    1. POPlace all output dlls in common directory from Visual Studio
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSamuel Meacham
    1. USSamuel Meacham
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis still leaves me with one of two problems: Either (if I copy everything from bin) I risk copying too much and overwriting stuff from other projects, or (if I copy only the dll that is the result of the project) I risk ending up with too little in the builds folder, since dependencies that are needed could be left out. Is there no middle way?
      singulars
      1. PO
      1. USTomas Lycken
    2. CO+1 this is exactly what i would have suggested. @Tomas, do you realise that you can filter the copy even more closely: `xcopy "$(TargetDir)*.dll" "c:\common\" /Y` to copy only the dlls. If that doesn't quite get everything then you could add another more specific copy command as well. This really isn't much of a hassle, its only a couple of minutes work and one or two test builds, and if you apply the right filtering to the `xcopy` then it is also low maintenance.
      singulars
      1. PO
      1. USslugster
    3. CO@Tomas - you could use [Robocopy](http://ss64.com/nt/robocopy.html) instead and use exclusion/inclusion options to get around those scenarios.
      singulars
      1. PO
      1. USHobo Spider
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload