2.0 Manifest Based Activation
Open Packaging Format OPF 2.0.1 v1.0v1.0.1. Draft Document September 11, 2007Recommended Specification September 4, 2010.
Windows activation does not work when the sppsvc.exe process is not started automatically for a long time.
Any framework that implements the OSGi standard provides an environment for the modularization of applications into smaller bundles. Each bundle is a tightly coupled.
1.0: Overview
This specification, the Open Packaging Format OPF, is one third of a triumvirate of modular specifications that make up the EPUB publication format. EPUB enables the creation and transport of reflowable digital books and other types of content as single-file digital publications that are interoperable between disparate EPUB-compliant reading devices and applications. EPUB encompasses a content markup standard Open Publication Structure – OPS, a container standard Open Container Format – OCF, and this specification, a packaging standard.
In order for electronic-book technology to achieve widespread success in the
marketplace, Reading Systems need to have convenient access to a large number and
variety of titles. Another related specification, the Open
Publication Structure OPS Specification, describes a standard for
representing the content of electronic publications and is meant to reduce barriers to
the proliferation of content. Specifically, the specification is intended to:
Give publication tool providers and content providers e.g. publishers, authors,
and others who have content to be displayed minimal and common guidelines that ensure
fidelity, accuracy, accessibility, and adequate presentation of electronic content over
various Reading Systems; and
Build on established content format standards; and
Define a standard means of content description in order for electronic books to
move smoothly through the distribution chain.
This document, the Open Packaging Format OPF Specification, defines the mechanism by
which the various components of an OPS publication are tied together and provides
additional structure and semantics to the electronic publication. Specifically, OPF:
Describes and references all components of the electronic publication e.g. markup
files, images, navigation structures.
Provides publication-level metadata.
Specifies the linear reading-order of the publication.
Provides fallback information to use when unsupported extensions to OPS are
employed.
Provides a mechanism to specify a declarative table of contentsglobal navigation structure the NCX.
This OPF specification is separate from the OPS markup specification to modularize the
described packaging methodology and the described content. This will help facilitate
the use of this packaging technology by other standards bodies e.g.
DAISY in non-OPS contexts.
A third specification, the OEBPSOpen Container Format OCF Specification, defines the
standard mechanism by which all components of an electronic publication can be packaged
together into a single file for transmission, delivery and archival.
Together, these three standards constitute EPUB.
Content Provider
A publisher, author, or other information provider who provides a publication to one
or more Reading Systems in the form described in this specification and the OPS
specification.
Deprecated
A feature that is permitted, but not recommended, by this
specification. Such features might be removed in future revisions. Conformant Reading
Systems must support deprecated features.
EPUB
The publication format as defined by the OCF 2.0.1, OPF 2.0.1, and OPF 2.0.1 specifications.
EPUB Publication
A collection of OPS Documents, an OPF Package file, and other files, typically in a variety of media types, including structured text and graphics, packaged in an OCF container that constitute a cohesive unit for publication, as defined by the EPUB standards.
EPUB Reading System or Reading System
A combination of hardware and/or software that accepts EPUB Publications and makes them available to consumers of the content. Great variety is possible in the architecture of Reading Systems. A Reading System may be implemented entirely on one device, or it may be split among several computers. In particular, a reading device that is a component of a Reading System need not directly accept OCF-Packaged EPUB Publications, but all Reading Systems must do so. Reading Systems may include additional processing functions, such as compression, indexing, encryption, rights management, and distribution.
Extended Module
A module of a modularized XML vocabulary i.e. a set of named modules is defined in
its specification that is not mandated to be supported by its specification e.g.
the XHTML ruby or forms modules in the OPS context.
Inline XML Island
An inline XML Island is an XML document fragment using a non-Preferred Vocabulary or
using an Extended Module that exists within an XHTML Preferred Vocabulary document
within an OPS Publication.
NCX
A declarative table of contentsglobal navigation definition the Navigation Center eXtended or NCX.
OCF
The OEBPSOpen Container Format defines a mechanism by which all components of an OPS
Publication can be combined into a single file-system entity. OCF is defined by the OCF Specification.
OEBPS
The Open Publication Structure. Previous versions of this specification
OPF and its related specification, OPS, were unified into the single OEBPS
specification. For this version, OEBPS was broken into separate OPF and OPS
specifications to aid modular adoption of the specifications. OEBPS 1.2 was the
highest version of the previous unified specification.
OPF
The Open Packaging Format this standard defines the mechanism by which all
components of a published work conforming to the OPS standard including metadata,
reading order and navigational information are packaged into an OPS Publication.
OPF Package Document
An XML Document that describes an OPS Publication and references all files used by
the OPS Publication that are not part of the OPF Package Document itself. It
identifies all other files in the Publication and provides descriptive information
about them. The OPF Package Document is defined by this specification and is valid to
the OPF Package Schema defined herein.
The root file of the OPF Package Document should use the
. opf extension. This XML file may
refer to other XML files via XML s general entity mechanism, but those files
must not use the. opf file
extension. This construction could be used to simplify the creation of OPF Package
Documents for very large Publications. However, the most common case is for the OPF
Package Document to be a single XML file using the. opf
extension.
OPS
The Open Publication Structure the sister-standard to this standard defines the
markup necessary to construct OPS Content Documents. OPS is defined by the OPS Specification.
OPS Content Document
An XHTML, DTBook, or out-of-line XML document that conforms to the OPS specification
that can legally appear in the OPF Package Document spine.
OPS Core Media Type
A MIME media type, defined in the OPS Specification, that all Reading Systems
must support.
OPS Publication
A collection of OPS Content Documents, an OPF Package Document, and other files,
typically in a variety of media types, including structured text and graphics, that
constitute a cohesive unit for publication.
Out-of-Line XML Island
An Out-Of-Line XML Island is an XML document that exists within an OPS Publication
and is either not authored using a Preferred Vocabulary or is authored using a
Preferred Vocabulary but uses Extended Modules. It is an entirely separate, complete,
and valid XML document.
Preferred Vocabulary
XML consisting only of OPS-supported XHTML markup and/or DTBook markup.
Reader
A person who reads a publication.
Reading System
A combination of hardware and/or software that accepts OPS Publications likely
packaged in an OCF Container and makes them available to consumers of the content.
Great variety is possible in the architecture of Reading Systems. A Reading System
may be implemented entirely on one device, or it
may be split among several computers. In particular, a
Reading Device that is a component of a Reading System need
not directly accept OPS Publications, but all Reading Systems must do so. Reading Systems may include
additional processing functions, such as compression, indexing, encryption, rights
management, and distribution.
See EPUB Reading System.
XML Document
An XML Document is a complete and valid XML document as defined in XML 1.1
An XML Document is a complete and valid XML document as defined in XML 1.0 Fourth Edition
XML Document Fragment
Referred to as either a document fragment or as an XML Document Fragment, as defined
in Document Object Model Level 1 but
with the additional requirement that they be well-formed.
XML Island
An Inline XML Island or an Out-of-Line XML island.
XML Namespaces
Referred to as XML namespaces, or just namespaces, these must conform to XML
Namespaces
This specification combines subsets and applications of other specifications. Together,
these facilitate the construction, organization, presentation, and unambiguous
interchange of electronic documents:
OPF is based on XML because of XML s generality and
simplicity, and because XML documents are likely to adapt well to future technologies
and uses. XML also provides well-defined rules for the syntax of documents, which
decreases the cost to implementers and reduces incompatibility across systems.
Further, XML is extensible: it is not tied to any particular type of document or set
of element types, it supports internationalization, and it encourages document markup
that can represent a document s internal parts more directly, making them amenable to
automated formatting and other types of computer processing.
Reading Systems must be XML processors as defined in XML
1.10. All OPF Package Documents must be valid XML documents
according to the OPF Package Schema.
Reading Systems may support XML 1.1, but this feature is deprecated in version 2.0.1 in favor of XML 1.0. Support for XML 1.1 will be removed in the next version of the specification.
The keywords must, must not,
required, shall, shall not, should, recommended, may, and optional in this document must be interpreted as
described in RFC 2119.
This section defines conformance for OPF Package Documents, and Reading Systems that
process those Documents.
2.0: The OPF Package Document
A publication conforming to this specification must include
exactly one XML OPF Package Document, which specifies the OPS Content Documents, images,
and other objects that make up the OPS Publication and how they relate to each other.
The OPF Package Document should be named
ending in the extension . opf, in order to make it readily identifiable within the group
of files making up the publication. The OPS Package Document is of MIME media type
application/oebps-package xml. This specification does not
define means for physically bundling files together to make one data transfer object
such as using zip or tar ; the OEBPSOpen Container Format OCF specifies this
functionality.
This specification neither precludes nor requires the inclusion of the OPF Package Schema
in a Publication.
The major parts of the OPF Package Document are:
Package Name
A unique identifier for the OPS Publication as a whole.
Metadata
Publication metadata title, author, publisher, etc..
Manifest
A list of files documents, images, style sheets, etc. that make up the publication.
The manifest also includes fallback declarations for files of types not supported by
this specification.
Spine
An arrangement of documents providing a linear reading order.
Tours Deprecated
A set of alternate reading sequences through the publication, such as selective views
for various reading purposes, reader expertise levels, etc.
Guide
A set of references to fundamental structural features of the publication, such as
table of contents, foreword, bibliography, etc.
An OPF Package Document must be a valid XML document conforming
to the OPF Package schema Appendix A. An informal outline of the package is
as follows:
metadata
manifest
spine
guide
The following sections describe the parts of the OPF Package Document.
The required metadata element is
used to provide information about the publication as a whole. It may contain Dublin Core metadata elements
directly or within a now deprecated dc-metadata
sub-element. Supplemental metadata can also be specified directly or within a now
deprecated x-metadata sub-element.
Reading Systems must allow the specification of the deprecated
dc-metadata and x-metadata
elements. Newly created OPS 2.0 packages should not create
dc-metadata or x-metadata
elements. If the dc-metadata element is used, all
dc elements must go in
dc-metadata and all other metadata elements, if any, must go into
x-metadata. If the dc-metadata element is not used, all metadata elements must go directly in the metadata element.
The required metadata or
dc-metadata deprecated elements contain specific
publication-level metadata as defined by the Dublin Core Metadata Initiative The descriptions below
are included for convenience, and the Dublin Core s own definitions take precedence
see
One or more optional instances of a meta element, analogous to the XHTML 1.1 meta element but applicable to the publication as a whole,
may be placed within the metadata
element or within the deprecated x-metadata element. This
allows content providers to express arbitrary metadata beyond the data described by the
Dublin Core specification. Individual OPS Content Documents may include the meta element directly as in
XHTML 1.1 for document-specific metadata. This specification uses the OPF Package
Document alone as the basis for expressing publication-level Dublin Core metadata.
For example:
metadata xmlns:dc
xmlns:opf
Tale of Two Cities
Charles Dickens
The XML namespace mechanism see is
used to identify the elements used for Dublin Core metadata without conflict. The
metadata or dc-metadata
deprecated elements may contain any number of instances of any Dublin Core
elements. Dublin Core metadata elements may occur in any order; in fact, multiple
instances of the same element type e.g. multiple Dublin Core creator elements can be interspersed with other metadata elements
without change of meaning.
Each Dublin Core field is represented by an element whose content is the field s value.
At least one of each of Dublin Core title, identifier and language must be included in the metadata element.
Dublin Core elements, like any other elements in the OPF Package Document, may have an id attribute specified. At
least one Dublin Core identifier, which is referenced from
the package unique-identifier attribute, must have an id specified.
Because the Dublin Core metadata fields for creator and
contributor do not distinguish roles of specific
contributors such as author, editor, and illustrator, this specification adds an
optional role attribute for this purpose. See Section 2.2.6 for a discussion of role.
To facilitate machine processing of Dublin Core creator
and contributor fields, this specification adds the
optional file-as attribute for
those elements. This attribute is used to specify a normalized form of the contents.
See Section 2.2.2 for a discussion of file-as.
This specification also adds a scheme attribute to the
Dublin Core identifier element to provide a structural
mechanism to separate an identifier value from the system or authority that generated
or defined that identifier value. See Section 2.2.10 for a discussion of scheme.
This specification also adds an event attribute to the
Dublin Core date element to enable content providers to
distinguish various publication specific dates for example, creation, publication,
modification. See Section 2.2.7 for a discussion of event. For example:
package version 2.0 xmlns
unique-identifier BookId
Alice in Wonderland
en
123456789X
Lewis Carroll
There are no attributes for the elements within metadata defined by Dublin Core only
the elements contents are so defined. In the above example, the specification of the
OPF namespace on the metadata element is present to
resolve the scheme and role attributes used in the identifier
and creator elements, respectively.
For compatibility with Guidelines for implementing Dublin Core in XML
this specification allows xsi:type attribute for metadata items that can be given
using some sort of encoding scheme and xml:lang attribute when an item can be given
using human-readable text. Elements that allow xsi:type attribute are identifier,
language, date, format and type. Elements that allow xml:lang attribute are: title,
contributor, coverage, creator, description, publisher, relation, rights, source,
and subject. This specification does not impose any specific rules for these
attributes with possible exception of heuristics that use xml:lang described
below.
The following subsections describe the individual Dublin Core metadata elements.
Following manifest, there must be one and only one spine element, which
contains one or more itemref elements. Each itemref references an OPS Content Document designated in the
manifest. The order of the itemref elements organizes the associated OPS Content Documents into
the linear reading order of the publication.
Each itemref in spine
must not reference media types other than OPS Content
Documents or documents whose fallback chain includes an OPS Content Document. An OPS
Content Document must be of one of the following media types:
application/xhtml xml, application/x-dtbook xml, the deprecated text/x-oeb1-document, and Out-Of-Line XML Island with required fallback. When a document with a
media type not from this list or a document whose fallback chain doesn t include a
document with a media type from this list is referenced in spine, Reading Systems must not include it as
part of the spine.
As items appearing in the spine must either be OPS
Content Documents or items with a fallback chain that includes an OPS Content, it is
possible to have a fallback chain for a spine item that
falls over another OPS Core Media type. For example, a spine itemref could reference a PDF
document, that falls back to a PNG image, that in turn falls back to a OPS XHTML
Content Document. It is valid for this item to appear in the spine because the fallback chain includes in this case terminates
with an OPS Content Document.
In addition, a specific spine item from the
perspective of its id attribute value in manifest must not appear more than once in spine.
All OPS Content Documents that are part of the publication i.e. are listed in the
manifest which are potentially reachable by any reference mechanism allowed in this
specification must be included in the spine. Such reference mechanisms include, as a partial list, hypertext
links within OPS Content Documents, and references by the NCX, Tours and Guide.
Should a Reading System encounter, by such reference, an OPS Content Document not
listed in spine as required in this specification, the
Reading System should add it to spine the placement at the discretion of the Reading System and
assign the value of the linear attribute to no see next.
For each itemref, the publication author may specify the optional linear attribute
to designate whether the associated OPS Content Document is primary linear yes, which is the default when linear is not present or auxiliary linear no. It is important that the publication author include
some kind of internal reference, such as a hypertext link, to any OPS Content Document
that is declared to be auxiliary; it is recommended that
references be added to NCX for all auxiliary content. At least one itemref in spine must be declared primary.
Specifying whether an OPS Content Document is primary or auxiliary is useful for
Reading Systems which opt to present auxiliary content differently than primary
content. For example, a Reading System might opt to render auxiliary content in a popup
window apart from the main window which presents the primary content. For an example
of the types of content that may be considered auxiliary, refer to the example below
and the subsequent discussion.
Reading Systems are not required to differentiate between
primary and auxiliary content, and for the requirements and recommendations given in
this section may consider all OPS Content Documents in
spine to be primary, regardless of the value of the
linear attribute.
The linear attribute also maintains compatibility
with OEBPS 1.x, where not all reachable OEBPS content documents were required to be
listed in the spine. For upgrading an OEBPS Publication to
OPS, every unlisted, reachable content document in the OEBPS 1.x Publication
should be assigned linear no.
Reading Systems are to use the ordered itemref
information in spine to present the publication during
reading. Reading Systems must recognize the first primary OPS
Content Document in spine to be the beginning of the main
reading order of the publication. Successive primary OPS Content Documents form the
remainder of the main reading order in the same order given in spine. Reading Systems may use next-page
style functionality when moving from one primary OPS Content Document to the next
primary one in spine.
The spine element must
include the toc attribute, whose value is the the
id attribute value of the required NCX document declared in manifest
see Section 2.4.1.
Example illustrating spine and the optional
linear attribute:
item id intro
href intro.html
media-type application/xhtml xml /
item id c1
href chap1.html
item id c1-answerkey
href chap1-answerkey.html
item id c2
href chap2.dtb
media-type application/x-dtbook xml /
item id c2-answerkey
href chap2-answerkey.html
item id c3
href chap3.html
item id c3-answerkey
href chap3-answerkey.html
item id note
href note.html
item id f1
href fig1.jpg
media-type image/jpeg /
item id f2
href fig2.jpg
item id f3
href fig3.jpg
item id ncx
href toc.ncx
media-type application/x-dtbncx xml /
In the above example, the publication author set linear no on four of the eight OPS Content Documents listed in
spine, designating these content documents to be
auxiliary. Three of the four are answer keys, and the fourth is a note of some sort;
all four are auxiliary to the main flow of the book and may be viewed separately from
the main flow.
Reading Systems which recognize and render auxiliary content separate from primary
content will set the main reading order to be the four primary OPS Content Documents:
intro, c1,
c2 and c3. The
auxiliary content documents will be rendered by such Reading Systems, upon activation
such as through a hypertext link or entry in NCX, in some manner distinct from the
main reading order. It is important that the publication author provide the necessary
references to the auxiliary content documents, otherwise this content might not be
reachable in some auxiliary-aware Reading Systems.
Reading Systems which opt to ignore linear no and
set all itemref to be primary, as allowed in this
specification, will assign all eight OPS Content Documents to the main reading order in
the order given. This is especially useful for Reading Systems which provide print
output, where it is important that all the information in the OPS Content Documents be
printed in an author-determined linear order.
A Reading System may, at its discretion, provide both
rendering options to the user.
In order to enable ease of navigation and provide greater accessibility, the OPF
Package Document supports a Navigation Center eXtended, the NCX. This is a concept
and implementation that has been standardized by the DAISY Consortium.
This specification uses the NCX defined in the DAISY/NISO Standard, formally the
. The NCX is a portion Section 8 of this comprehensive
multimedia standard. The DAISY Consortium maintains the NCX DTD. No modifications to
the DTD are necessary for use with OPF. In the future the DAISY/NISO Advisory
Committee will consider modularizing the NCX and changing terminology to be more in
line with ebooks, multimedia publications and other electronic document usage.
Some optional elements and metadata items are not needed to
implement the NCX for this specification. The sections below have been changed to
normatively reference the DAISY/NISO standard for the NCX rather than duplicating it
here. All exceptions are described in Section 2.4.2, below.
The Navigation Control file for XML applications NCX exposes the hierarchical
structure of a Publication to allow the user to navigate through it. The NCX is
similar to a table of contents in that it enables the reader to jump directly to
any of the major structural elements of the document, i.e. part, chapter, or
section, but it will often contain more elements of the document than the publisher
chooses to include in the original print table of contents. It can be visualized as
a collapsible tree familiar to PC users. Its development was motivated by the need
to provide quick access to the main structural elements of a document without the
need to parse the entire documents. Other elements such as pages, footnotes,
figures, tables, etc. can be included in separate, nonhierarchical lists and can be
accessed by the user as well see the below informative example.
It is important to emphasize that these navigation features are intended as a
convenience for users who want them, and not a burden to those who do not. The
alternative guide to the book may be provided for
those users not requiring the navigation features of the NCX.
Reading Systems must support NCX.
OPS Publications must include an NCX.
Reading Systems should support the NCX.
A Reading System should have the ability to, at user selection,
provide access to the NCX navMap in a fashion that
allows the user to activate the links provided in the navMap,
thus relocating the application s current reading position to the destination described
by the selected NCX navPoint.
The behavioral expectations described above apply to the NCX pageList
and navList as well, if the given NCX contains said elements.
Reading System implementors should be aware that in a forthcoming major revision of the
EPUB specification, it likely will become a compliance criteria for Reading Systems to support the
NCX navMap, pageList and
navList as described above.
Like all other Publication components, the NCX must be
included as an item in the manifest with media-type of
application/x-dtbncx xml. The NCX-referencing
item must not contain any
fallback information required-namespace,
fallback or fallback-style attributes.
If a Publication includes an NCX, theThe item that
describes the NCX must be referenced by the spine toc attribute.
The NCX file must be a valid XML document conforming to
ncx-2005-1.dtd and comply with the additional normative
requirements defined in
, with the exception of the playOrder attribute, which is optional in EPUB NCX.
The version and xmlns attributes on the ncx
element must be explicitly specified in the document
instance, using values drawn from the above-named DTD.
Any NCX that contains a DOCTYPE that references the canonical NCX
DTD must honor that DTD, thus including the
playOrder attribute in all locations
where it is required. NCX documents that do not contain a DOCTYPE
may omit the
playOrder attribute.
navMap is a required element
in the NCX; it provides navigational access to the major hierarchical structure of the publication.
pageList must be included if the publication
is designed to allow the user to navigate to pages. One or several navList s
may be included to allow navigation to other arbitrary constructs in
the content see the below informative example.
The URI specified by the src of the content element for
navMap, pageList, and
navList elements must resolve to OPS
Content Document fragments.
Example illustrating an NCX with a navMap, a pageList, and a navList containing a list of illustrations:
Selections from Great Pictures, As Seen and Described by Famous Writers
Esther Singleton
Chapter 1
Chapter 1.1
Chapter 2
1
2
List of Illustrations
Portratit of Georg Gisze Holbein
The adoration of the lamb Van Eyck
Much as a tour-guide might assemble points of interest into a set of sightseers tours,
a content provider could assemble selected parts of a publication into a set of tours
to enable convenient navigation.
An OPS Package Document may, but need not, contain one
tours element, which in turn contains one or more
tour elements. Each tour
must have a title attribute,
intended for presentation to the user. Reading Systems may use
tours to provide various access sequences to parts of the
publication, such as selective views for various reading purposes, reader expertise
levels, etc. Because Reading Systems are not required to
implement tour support, content providers should also provide
other means of accessing content referenced from tours.
Each tour element contains one or more site elements, each of which must have an
href attribute and a title attribute. The href attribute
must refer to an OPS Content Document included in the
manifest, and may include a
fragment identifier as defined in section 4.1 of RFC 2396 see Each site element specifies a starting point from which the reader can
explore freely. Reading Systems may use the bounds of the
referenced element to determine the scope of the site. If a fragment identifier is
not used, the scope is considered to be the entire document. This specification does
not require Reading Systems to mark or otherwise identify
the entire scope of a referenced element. The order of site elements is presumed to be significant, and should be used by Reading Systems to aid navigation.
site title Chicken Fingers
href appetizers.html r3 /
site title Chicken a la King
href entrees.html r5 /
Appendices
Appendix A: The OPF Package Schema
grammar xmlns ns
datatypeLibrary
. --
Title:
Relax NG Schema for the Open Packaging
Format OPF version 2.0
Version:
2.0
Revision:
20070222
Authors:
This Version 2.0 :
Peter Sorotokin
--
yes
no
zerooneOrMore
Appendix C: Acknowledgements
The working group wishes to specifically acknowledge the contributions of the following
individuals. Peter Sorotokin for authoring the OPS and OPF
RelaxNG schemas, creation of the NVDL definition of OPS, and general technical acumen.
Ben Trafford for the concept and drafting of XML Islands,
as well as overall technical participation, and the XML templates used to produce the
specifications. George Kerscher for drafting the OPF NCX
section, providing consistent accessibility direction and broad technical input.
Brady Duga and Jon Noring for
directional contributions, specification editing and providing continuity with the
historic OEBPS 1.2 effort. Garth Conboy for working group
leadership and motivation, specification drafting and technical contributions.
Appendix D: Supporting Information Errata
For additional information about all IDPF specifications including sample files,
specification implementations and other information, please visit our public forums at
If errors in the specifications
are identified following publication, please post these errors to the forums. The
responsible Working Group will review the errors and post pending corrections to the
specifications if required or necessary. Corrections will be incorporated into
subsequent versions of the specifications.
Open Packaging Format (OPF) 2.0.1 v1.0
OS: Windows 7 64 bit using Visual Studio Pro 2012 with. NET 4.5 installed.
I used the Publish option within Visual Studios and ensured that I had clicked the Sign the clickOnce manifest and Sign the Assembly. It will still not run on another computer and says I do not have a valid XML signature. I have pasted the error message below.
I have also read: How to move a ClickOnce deployment package, Do I have to sign my ClickOnce manifest.. Exception reading manifest from file: the manifest may not be valid or the file could not be opened and several others.
I need to be able to deploy my program on. NET 4.0 at the minimum and I do not have access to another version of Visual Studios. Thanks in Advance.
complete Error Below:
PLATFORM VERSION INFO
Windows : 5.1.2600.196608 Win32NT
Common Language Runtime : 2.0.50727.3603
System.Deployment.dll : 2.0.50727.3053 netfxsp.050727-3000
mscorwks.dll : 2.0.50727.3603 GDR.050727-3600
dfdll.dll : 2.0.50727.3053 netfxsp.050727-3000
dfshim.dll : 4.0.31106.0 Main.031106-0000
SOURCES
Deployment url : file:///C:/Documents 20and 20Settings/Administrator/Desktop/EatonWizard.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
Activation of C: Documents and Settings Administrator Desktop EatonWizard.application resulted in exception. Following failure messages were detected:
Exception reading manifest from file:///C:/Documents 20and 20Settings/Administrator/Desktop/EatonWizard.application: the manifest may not be valid or the file could not be opened.
Manifest XML signature is not valid.
SignatureDescription could not be created for the signature algorithm supplied.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
10/10/2012 :02 PM : Activation of C: Documents and Settings Administrator Desktop EatonWizard.application has started.
ERROR DETAILS
Following errors were detected during this operation.
10/10/2012 :02 PM System.Deployment.Application.InvalidDeploymentException ManifestParse
- Exception reading manifest from file:///C:/Documents 20and 20Settings/Administrator/Desktop/EatonWizard.application: the manifest may not be valid or the file could not be opened.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ManifestReader.FromDocument String localPath, ManifestType manifestType, Uri sourceUri
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass SubscriptionStore subStore, Uri sourceUri, TempFile tempFile, SubscriptionState subState, IDownloadNotification notification, DownloadOptions options, ServerInformation serverInformation
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass SubscriptionStore subStore, Uri sourceUri, TempFile tempFile, SubscriptionState subState, IDownloadNotification notification, DownloadOptions options
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String errorPageUrl
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker Object state
--- Inner Exception ---
System.Deployment.Application.InvalidDeploymentException SignatureValidation
- Manifest XML signature is not valid.
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature Stream s
System.Security.Cryptography.CryptographicException
- SignatureDescription could not be created for the signature algorithm supplied.
- Source: System.Security
at System.Security.Cryptography.Xml.SignedXml.CheckSignedInfo AsymmetricAlgorithm key
at System.Security.Cryptography.Xml.SignedXml.CheckSignatureReturningKey AsymmetricAlgorithm signingKey
at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify CmiManifestVerifyFlags verifyFlags
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
Aug 10, 2012 Jenfeng s blog discusses in details about registration free COM/. Net interop. Please see.
"Manifest XML signature is not valid"
Can t install RDS CALs by using a web browser or telephone on a Windows Server 2012-based license server.
The second application manifest, describes the COM components which are exposed in the assembly. It needs to be set as the application manifest which resides as a.
Tour Start here for a quick overview of the site Help Center Detailed answers to any.
