Databases
StackOverflow2013
Postsdbo
POBest practices for merging assemblies?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest practices for merging assemblies?
    primarykey
    data
    text
    <p>I am wondering what are the heuristics when creating releases of libraries to be included in other projects in relation to dependencies and if I should include them or not.</p> <p>My problem is the following:</p> <p>I have a CommonUtilities library that provides as the name implies a set of utilities that can be used in more than one place. Dependencies of CommonUtilities include log4net.dll (the logging framework) and Oracle.DataAccess.dll (database driver). </p> <p>I have another project called MyProject that I want to include CommonUtilities in. MyProject also depends on Oracle.DataAccess.</p> <p>If I use ILMerge and merge CommonUtilities into a single assembly CommonUtilities.dll and reference that from MyProject everything compiles but I am sure I should explicitly reference Oracle.DataAccess from MyProject as it is a dependency and not use the assembly merged into CU. Adding a reference to Oracle.DataAccess as well results in ambiguous using statements as there are two Oracle.DataAccess assemblies referenced.</p> <p>Using ILMerge /Internalize in my case results in compile errors as types from the internalized Oracle.DataAccess assembly are being returned from CommonUtilities and as they are marked internal MyProject does not recognize the type returned.</p> <p>The only way to make this work is simply to not merge this particular assembly (Oracle.DataAccess) into CommonUtilities and only reference that from MyProject. This in turn creates a new problem: Which Oracle.DataAccess.dll should I reference - the dependency distributed with CommonUtils or not?</p> <p>Are there other ways to go about all this?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USFadeproof
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBest practices for merging assemblies?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBest practices for merging assemblies?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POBest practices for merging assemblies?
      1. USRob Stevenson-Leggett
      1. VTFavorite
    1. COI scratch my head at ilmerge - I don't see an advantage to placing all assemblies in a single file. Anyone care to enlighten me?
      singulars
      1. POBest practices for merging assemblies?
      1. UScfeduke
 

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