Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7024773
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T23:53:09+00:00 2026-05-27T23:53:09+00:00

My application creates a ClickOnce application via the command line tool Mage . If

  • 0

My application creates a ClickOnce application via the command line tool Mage. If I build the ClickOnce application on Windows XP 32-bit (Visual Studio 2008), and double click the xxx.application file, it’s working fine.

The same project run on Windows 7 64 bit (Visual Studio 2008), and the ClickOnce application is created fine, but starting the xx.application file generates an error (see below).

I’m using the MS-SDK 6.0A "…Program Files\Microsoft SDKs\Windows\v6.0A\Bin\mage.exe"

Why is this?

Error message

PLATFORM VERSION INFO

    Windows                  : 6.1.7601.65536 (Win32NT)
    Common Language Runtime  : 4.0.30319.239
    System.Deployment.dll    : 4.0.30319.1 (RTMRel.030319-0100)
    clr.dll                  : 4.0.30319.239 (RTMGDR.030319-2300)
    dfdll.dll                : 4.0.30319.1 (RTMRel.030319-0100)
    dfshim.dll               : 4.0.31106.0 (Main.031106-0000)


SOURCES

    Deployment url           : file:///C:/m4/branches/oebb2.2.0/Deployment/M4Desktop.application


IDENTITIES

    Deployment Identity      : M4Desktop.app, Version=2.2.0.26921,
    Culture=neutral, PublicKeyToken=7825390df6ab8bb8,
    processorArchitecture=msil

APPLICATION SUMMARY

    * Installable application.


ERROR SUMMARY

    Below is a summary of the errors, details of these
    errors are listed later in the log.
    * Activation of C:\m4\branches\oebb2.2.0\Deployment\M4Desktop.application resulted in
      exception. Following failure messages were detected:
      + Exception reading manifest from file:///C:/m4/branches/oebb2.2.0/Deployment/M4Desktop_2.2.0.26921/M4Desktop.exe.manifest:

        the manifest may not be valid or the file could not be opened.

      + Application manifest is not semantically valid.
      + Specified <entryPoint> is not valid. Check that the path to the entrypoint is
        well-formed and the entrypoint exists in the deployment.


COMPONENT STORE TRANSACTION FAILURE SUMMARY

    No transaction error was detected.


WARNINGS

    There were no warnings during this operation.

OPERATION PROGRESS STATUS     * [22.12.2011 10:42:49] : Activation of
C:\m4\branches\oebb2.2.0\Deployment\M4Desktop.application has started.
    * [22.12.2011 10:42:49] : Processing of deployment manifest has
successfully completed.     * [22.12.2011 10:42:49] : Installation of the
application has started.


ERROR DETAILS     Following errors were detected during this operation.
    * [22.12.2011 10:42:49]
System.Deployment.Application.InvalidDeploymentException
(ManifestParse)

      - Exception reading manifest from file:///C:/m4/branches/oebb2.2.0/Deployment/M4Desktop_2.2.0.26921/M4Desktop.exe.manifest:
        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.DownloadApplicationManifest(AssemblyManifest deploymentManifest, String targetDir, Uri deploymentUri, IDownloadNotification notification, DownloadOptions options, Uri&appSourceUri, String& appManifestPath)
        at System.Deployment.Application.DownloadManager.DownloadApplicationManifest(AssemblyManifest deploymentManifest, String targetDir, Uri deploymentUri, Uri&appSourceUri, String& appManifestPath)
        at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
        at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState&subState, ActivationDescription actDesc)
        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 (ManifestSemanticValidation)
        - Application manifest is not semantically valid.
        - Source: System.Deployment
        - Stack trace:
              at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemanticsForApplicationRole()
              at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)

        --- Inner Exception ---
        System.Deployment.Application.InvalidDeploymentException (InvalidManifest)
        - Specified <entryPoint> is not valid. Check that the path to the entrypoint is well-formed and the entrypoint exists in the deployment.
        - Source: System.Deployment
        - Stack trace:
            at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemanticsForApplicationRole()

COMPONENT STORE TRANSACTION DETAILS
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T23:53:10+00:00Added an answer on May 27, 2026 at 11:53 pm

    In my case the problem was non-matching values processorArchitecture between the <assemblyIdentity> and <entryPoint> tags.

    When generating the manifest via command line Mage I didn’t add the -p x86 option.

    Some DLL files included in the ClickOnce application where built with x86 solution, but Mage generated assemblyIdentity with processorArchitecture=x86 by default.

    I’m working with both Visual Studio 2008 on Windows 7 64-bit and also Windows XP 32-bit.

    See below for relevant parts of the manifest file.

    Not working manifest

      <asmv1:assemblyIdentity
          name="M4Desktop.exe"
          version="2.2.0.27055"
          publicKeyToken="7825390df6ab8bb8"
          language="neutral"
          processorArchitecture="msil"
          type="win32" />
      <application />
      <entryPoint>
        <assemblyIdentity
            name="M4DesktopUpdater"
            version="1.0.0.0"
            publicKeyToken="D2F6EAED73E3B4FE"
            language="neutral"
            processorArchitecture="x86" />
        <commandLine
            file="M4DesktopUpdater.exe"
            parameters="" />
      </entryPoint>
    

    Working manifest

      <asmv1:assemblyIdentity
          name="M4Desktop.exe"
          version="2.2.0.27055"
          publicKeyToken="7825390df6ab8bb8"
          language="neutral"
          processorArchitecture="x86"
          type="win32" />
      <application />
      <entryPoint>
        <assemblyIdentity
            name="M4DesktopUpdater"
            version="1.0.0.0"
            publicKeyToken="D2F6EAED73E3B4FE"
            language="neutral"
            processorArchitecture="x86" />
        <commandLine
            file="M4DesktopUpdater.exe"
            parameters="" />
      </entryPoint>
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I've built an WPF application with visual studio 2008 and created an installer for
When publishing a Clickonce application though visual studio, there's a button Prerequisites... where you
I have an information retrieval application that creates bit arrays on the order of
We would like to deploy an application via ClickOnce but you really do need
I created my ClickOnce application witch will install a small windows form application that
my application creates a new instance of winword embedded in a windows form. new
Visual Studio 2005 I have developed an application using C#. I have created an
I am trying to publish my Windows Form Application using ClickOnce on the IIS
My application creates custom URIs (or URLs?) to identify objects and resolve them. The
The Vb.Net application creates a bitmap from scratch and either converts to a tiff

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.