Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is how I do it. Not sure if there is any other better way:</p> <ol> <li>Right-click on your solution from the Solution Explorer. Hover over "Add" and select "New Solution Folder". It's not really a folder and does not point to any Physical Folder. It's an abstract construct for grouping projects within a solution, but we'll use it for something else.</li> <li>Call it something like "Referenced Assemblies".</li> <li>Next, Right-click on your solution again and click on "Open Folder in Windows Explorer". In the windows explorer window that pops up add a new "Physical Folder" (this will be located right underneath the Solution's root folder).</li> <li>You can call it "Referenced Assemblies" so that the Solution Folder and Physical Folder share the same name so as to avoid confusion.</li> <li>Grab all those DLL's lurking everywhere (i.e. the <em>AjaxControlToolkit.dll</em> or the <em>DocumentFormat.OpenXml.dll</em> buried in program files) and copy (DO NOT DRAG - keep the originals where they are) them into the "Referenced Assemblies" folder in Windows Explorer (NOT IN THE SOLUTION).</li> <li>Now you can drag those copied dll's from the "Referenced Assemblies" Physical Folder in Windows Explorer into the "Referenced Assemblies" Solution Folder in Visual Studio's Solution Explorer.</li> <li>Go through each project in your solution and remove all references to the assemblies you will be referencing from the "Referenced Assemblies" folder.</li> <li>Add the references back in, but this time (under the project) right-click on "References", click "Add Reference...", select the "Browse" tab, click the folder icon with the green arrow (says "Up One Level" when hovering over it), double-click the "Reference Assemblies" folder, select all the dll's you wanna reference and click "OK".</li> </ol> <p>You're done. Now that your solution knows of these dll's and where to find them, when you check in your code (via SVN, TFS, or whatever) it will push them up and copy them down for others to use.</p> <p>If your using TortiseSVN you don't have to do anything if you're also using the <a href="http://ankhsvn.open.collab.net/" rel="noreferrer">AnkhSVN plug-in for Visual Studio</a>. It studies your solution file (just like TFS does) to find files referenced by the solution. In this case it will pick up on the new dll's being referenced by the "Referenced Assemblies" Solution Folder and automatically add source-control tracking before committing them (that is if you commit your solution changes from the Solution Explorer in Visual Studio like I do).</p> <p>Hope this helps.</p>
    singulars
    1. This table or related slice is empty.
    1. POStoring referenced Dlls in visual studio solution folder
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMikeTeeVee
    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 is how I currently do mine too. 50 bucks they add a better way to do this feature in like vs2020... (x_x)
      singulars
      1. PO
      1. USShawn Mclean
    2. CONote that you can't simply drag folders into a solution folder. So you should create a tree structure (with sub solution folders) that reflects the file system folders. This is a bit uncomfortable, but that's a built in limitation of VS.
      singulars
      1. PO
      1. USRon Klein
    3. CO@RonKlein Not sure what you mean. I never say to drag folders into the solution folder. My process works and it is probably the same method you use.
      singulars
      1. PO
      1. USMikeTeeVee
 

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