The primary assembly file

For example, if you've registered different versions of the PIAs in the global assembly cache, your project will automatically bind to the version of the assembly that was registered last, even if you specify a different version of the assembly on the COM tab of the Reference Manager dialog box. Some assemblies are added to a project automatically when an assembly that references them is added. For example, references to the Office. The following table lists the primary interop assemblies that are available for Office , Office and Office When you install and register the Office PIAs in the global assembly cache either with Office or by installing the redistributable package for the PIAs , the binding redirect assemblies are also installed only in the global assembly cache.

These assemblies ensure that the correct version of the primary interop assemblies is loaded at run time. For example, when a solution that references a Office assembly runs on a computer that has the Office version of the same primary interop assembly, the binding redirect assembly instructs the. NET Framework runtime to load the Office version of the primary interop assembly. For more information, see How to: Enable and disable automatic binding redirection.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Note Interested in developing solutions that extend the Office experience across multiple platforms? Note Some assemblies are added to a project automatically when an assembly that references them is added.

Submit and view feedback for This product This page. Asked 4 years, 7 months ago. Active 4 years, 6 months ago. Viewed 8k times. Improve this question. EMiller EMiller 4 4 silver badges 11 11 bronze badges. Add a comment. Active Oldest Votes. Improve this answer. Manuel Manuel 4 4 silver badges 5 5 bronze badges.

Hope this helps someone else! There are essentially three options here: chromFa. Konrad Rudolph Konrad Rudolph 4, 10 10 silver badges 38 38 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. You are presented with a bunch of options. In what cases would I prefer other genomes? There's rarely a good reason to use a hard-masked genome sometimes for blast, but that's it. For primary vs. If you happen to be using BWA, then the toplevel assembly would benefit you.

Note that none of these actually use soft-masking. Generally, you should use the soft-masked or unmasked primary assembly. Cross-species whole-genome aligners, especially older ones, do need to know soft-masked regions; otherwise they can be impractically slow for mammalian genomes. Modern read aligners are designed to work with repeats efficiently and therefore they don't need to see the soft mask.

Using the Ensembl version is discouraged due to its chromosome naming. We more often use "chr1" instead of "1" for GRCh At one point, Ensembl actually agreed to use "chr1" as well, but didn't make that happen due to technical issues, I guess. As to alternate haplotypes, most aligners can't work with them; no variant callers can take the advantage of these sequences, either.

When you align to a reference genome containing haplotypes with an aligner not supporting these extra sequences, you will get poor mapping results.

If you're doing whole genome - whole genome alignment rather than read alignment then using the softmasked genome is definitely best. Tools suitable for such large scale alignments task tend to skip marked repeats completely in their initial steps to prevent the build up of bogus short alignments that can have a massive performance impact in terms of time and memory usage. These files contains all sequence regions flagged as toplevel in an Ensembl schema.

Primary assembly contains all toplevel sequence regions excluding haplotypes and patches.