Databases
StackOverflow2013
Postsdbo
POCopying indirectly referenced assembly to output directory - assembly is missing
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCopying indirectly referenced assembly to output directory - assembly is missing
    primarykey
    data
    text
    <blockquote> <p><strong>Possible Duplicate:</strong><br> <a href="https://stackoverflow.com/questions/320295/how-does-copy-local-work">How does Copy-local work?</a> </p> </blockquote> <p>I have following situation:</p> <ul> <li>there's a project named OLAF.Tools, and that project references Microsoft.Data.SqlXml in C:\Program Files\SQLXML 4.0\bin\Microsoft.Data.SqlXml.dll. Reference Copy Local property is set to True. When I build that project in bin directory I can see both OLAF.Tools.dll and Microsoft.Data.SqlXml.dll</li> <li>there's a console application named OLAF.Generator, and that application references OLAF.Tools (I've added reference using Project tab). When I build that application in bin directory I can see only OLAF.Generator.exe and OLAF.Tools.dll - there's no Microsoft.Data.SqlXml.dll, what supprises me. Another wierd thing is that even though that dll is missing application is executing properly. </li> </ul> <p>So my questions are:</p> <ul> <li>why Microsoft.Data.SqlXml.dll is not copied to bin folder of OLAF.Generator console application?</li> <li>how application resolves directory where Microsoft.Data.SqlXml.dll can be found?</li> </ul> <p>Thanks,Pawel</p> <p>EDIT 1: (after response from <strong>Marc Gravell</strong>)</p> <p><strong>@Marc Gravell</strong>: Your answer gave me food for thought, as I could swore that I could always see indirectly dependant assemblies in main application's bin directory. And IMHO I don't agree with you - with all due respect :) </p> <p>Of course, references are not cascaded physically (we're are talking about strong relationship to classes, interfaces etc) - and it's exactly what I wanted to achieve when building OLAF.Tools library. That library provides a level of abstraction, it contains factories, and one factory accepts as a parameter string and returns interface. One particular implementation of that interface uses Microsoft.Data.SqlXml components. As a result, OLAF.Generator uses interface that is located in OLAF.Tools, but doesn't know about components in Microsoft.Data.SqlXml.</p> <p>Apart from that (I think we both know what I tried to explain in preceding paragraph), when building application, dependant assemblies should be copied (if Copy Local is set to TRUE). I just wrote sample application, Project B lib has reference to Project A lib, and Project C (console app) has reference to Project B. In Project C's bin directory I can see all: Project A.dll, Project B.dll &amp; Project C.exe. So in discussed scenario, the reason why Microsoft.Data.SqlXml doesn't end up in OLAF.Generator bin folder has something to do with that assembly itself.</p> <p>Does compiler/visual studio knows that Microsoft.Data.SqlXml is located in directory which is automatically probed (or it's in GAC) and this is the reason why that assembly is not copied?</p> <p>EDIT 2: I've just checked GAC, and indeed, Microsoft.Data.SqlXml.dll is installed in GAC.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USdragonfly
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCopying indirectly referenced assembly to output directory - assembly is missing
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCopying indirectly referenced assembly to output directory - assembly is missing
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCopying indirectly referenced assembly to output directory - assembly is missing
      1. This table or related slice is empty.
      1. VTUpMod
    1. COOccam's razor says that you don't actually have a dependency on the SqlXml assembly. Because it didn't get copied. *And* because it runs fine without it. Do check if it is installed in the GAC.
      singulars
      1. POCopying indirectly referenced assembly to output directory - assembly is missing
      1. USHans Passant
    2. CORe your edit: are you using a *project* reference (whereby it can inspect the needs, and it looks like it *will* include necessary files), or is it a *file* reference (whereby it looks like it can't and doesn't)?
      singulars
      1. POCopying indirectly referenced assembly to output directory - assembly is missing
      1. USMarc Gravell
    3. COOLAF.Tools uses file reference to ProgramFiles SqlXml dll, whereas OLAF.Generator uses project reference to OLAF.Tools, and in OLAF.Tools output bin folder I can see OLAF.Tools.dll & Microsoft.Data.SqlXml.dll, whereas in OLAF.Generator output bin I can see only OLAF.Generator.exe & OLAF.Tools.dll - Microsoft.Data.SqlXml.dll is missing
      singulars
      1. POCopying indirectly referenced assembly to output directory - assembly is missing
      1. USdragonfly
 

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