Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I personally have never installed any assemblies directly in the GAC (except as a purely academic exercise). I've heard the argument before about using an assembly from a centralized location that is accessed from several applications, and while that seems somewhat attractive, personally, it's not worth my time. Computers come with 320GB of hard disk space these days... my measly 160K assembly isn't going to make a dent in that, even if it's copied 5 times. (Of course, some could argue the "problem of the commons"... you know: "if every developer thought that way....", but I digress). The main reason I choose not to do this is because one particular application might rely on the assembly in one way, while another might rely on it another way. While in an ideal world, updates to this assembly should never affect the applications that rely on it, in reality, it often does. If I'm fixing a problem with an assembly because a particular application has issues with it, I'm unwittingly affecting the other applications that rely on that particular assembly. On the other hand, some might argue that this kind of situation makes us better programmers and makes our GAC-Shared assembly more bulletproof. That's great, but my job as a programmer isn't primarily to make myself a better programmer, but to write programs that work, and doing so, I will become a better programmer. </p> <p>So what's my vote? Keep away from the GAC. Let each application rely on the version of the assembly they're built to rely on. A bug exposed in that assembly by one application may never show up in the other applications, because they're using the assembly differently, so leave them be and you won't have to regression test 5 distinct applications every time your shared DLL gets patched. </p>
    singulars
    1. This table or related slice is empty.
    1. PORevisiting GAC Installations
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDavid Morton
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORevisiting GAC Installations
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COYeah, disk space not really my concern :) I appreciate the honesty of your answer but I have to argue that if two consumers of shared code exhibit different but correct behaviour then there's a question mark about the separation of the functionality. I think I see things the other way round - if I make myself a better programmer then, QED, I write better programs.
      singulars
      1. PO
      1. USDan Kendall
    2. COI'd say there's definitely a balance, however. Yes, you want to become a better programmer, and becoming a better programmer helps you to write better programs, but there are better ways to become a better programmer than by pressure-cooking assemblies in production.
      singulars
      1. PO
      1. USDavid Morton
    3. COI'm not sure I understand your "pressure-cooking" term. I agree entirely with the need for a balanced and pragmatic approach. The issue is that it seems your and others' responses to the GAC question could be paraphrased (and I merely do this to hilight my concern - not to belittle your opinion) as "we think the GAC is a good idea but we want to avoid the overhead of making our code work happily with it." Which is a rather jaundiced view of development to present in such blanket responses. I'd rather know the specific risks and make my own mind up. Please correct me if I'm wrong.
      singulars
      1. PO
      1. USDan Kendall
 

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