Databases
StackOverflow2013
Postsdbo
PODeploy distinct versions of common assembly via various SharePoint packages?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODeploy distinct versions of common assembly via various SharePoint packages?
    primarykey
    data
    text
    <p>I have Common.dll that's shared/used by (far more than) two SharePoint packages being deployed to the same GAC used by a single SharePoint instance. The shared assembly evolves from product deployment to product deployment, and it's not treated as a product in and of itself. It is not released, per se. It evolves only in the context of other SharePoint products/packages.</p> <p>The common assembly is primarily just a repository for highly reusable code. It's used only by a small internal team of developers.</p> <p>Branching/merging allows various products to take on the latest version of Common.dll whenever it suits the developers. Each product's development effort schedules the risk of taking on the new version of Common.dll.</p> <p>My need is to have those assemblies act in isolation from product to product -- from SharePoint package to SharePoint package.</p> <p>But that's not happening. Instead, every time I deploy, Common.dll is overwritten in the GAC such that all products using it receive the behavior of this most recent version of Common.dll. Depending on what that behavior is, it can break a product that hasn't been deployed in some time.</p> <p>I'm trying to prevent that deployment "surprise!" potential w/o having to treat Common.dll like a public product that has to carefully avoid breaking changes/etc.</p> <p>What technique do you use to preserve distinct versions of common assemblies when deploying various SharePoint packages to a single SharePoint instance's GAC?</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. USlance
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COIs each version of Common.dll being compiled with a different version in the 4 part name?
      singulars
      1. PODeploy distinct versions of common assembly via various SharePoint packages?
      1. USRich Bennema
    2. CO@RichBennema Does this answer your question?: Changing the AssemblyVersion attribute of a dependency assembly between deployments later causes SharePoint Web Part runtime errors. So, the AssemblyVersion of our Common.dll never changes.
      singulars
      1. PODeploy distinct versions of common assembly via various SharePoint packages?
      1. USlance
    3. COYes. Installing multiple versions of Common.dll, each with different version numbers, into the GAC is what I would have suggested.
      singulars
      1. PODeploy distinct versions of common assembly via various SharePoint packages?
      1. USRich Bennema
 

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