Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The "best practice" in this case, is to not fight the tool. It allows you to do what you want, but you'll get more work done and be able to focus on code if you just let the IDE organize your project for you.</p> <p>I would create an empty solution project called PdMagic.Common</p> <p>This will give you a file structure like</p> <pre><code>PdMagic.Common\ PdMagic.Common\PdMagic.Common.sln </code></pre> <p>then I generally add a src and libs folder (via the file system, not VS)</p> <p>inside the libs folder, i would place all my third party dependencies, and the src folder would hold all of my projects</p> <pre><code>PdMagic.Common\ PdMagic.Common\PdMagic.Common.sln PdMagic.Common\libs PdMagic.Common\libs\nunit PdMagic.Common\src </code></pre> <p>Next, in Visual Studio, I would right click on the Solution I just created, and click "Add -> New Project", I would specify that I wanted it created in the \src folder and call it PdMagic.Common.Math</p> <p>Now my folder structure would look like this</p> <pre><code>PdMagic.Common\ PdMagic.Common\PdMagic.Common.sln PdMagic.Common\libs PdMagic.Common\libs\nunit PdMagic.Common\src PdMagic.Common\src\PdMagic.Common.Math PdMagic.Common\src\PdMagic.Common.Math\PdMagic.Common.Math.csproj PdMagic.Common\src\PdMagic.Common.Math\Class1.cs </code></pre> <p>Then, as you add classes to your PdMagic.Common.Math project, they will go in the folder with the project file. This is how the IDE has the opinion we should work, and I think most developers go with it because trying to get any other layout on the file system would require too much fighting with the IDE. I know it can be hard to come from a different convention, and you instinctively want the same conventions in the new environment. However, if you stick with the conventions, (right or wrong in your opinion) you'll get more done because you won't be trying to force the IDE to do things the way you think they should be done.</p>
    singulars
    1. This table or related slice is empty.
    1. POVisual Studio: Add Item / Add as link rather than just Add
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USNerdFury
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POVisual Studio: Add Item / Add as link rather than just Add
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThat's exactly the kind of answer I was looking for. While you were writing it, I was doing some experimenting myself and came up with a (common) case that I'm not sure it can handle. I am targeting both Silverlight and WPF. Most of the source (.cs) is the same, but different assemblies must be built for each. So, I need to have PdMagic.Common.Math for SL and PdMagic.Common.Math for WPF. I think this requires two projects that both use the same Class1.cs. Could I trouble you to take this one step further? Thanks again for your answer.
      singulars
      1. PO
      1. USPete d'Oronzio
 

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