index > ClickOnce and Setup & Deployment Projects > Publishing Problem in RC1 - 8.05727.26 (v2.0.50215 getting instal...

Publishing Problem in RC1 - 8.05727.26 (v2.0.50215 getting instal...

I have recently moved to Publishing Problem in RC1 - 8.05727.26 from beta 2 (I uninstalled everything) and am planning to complete a commercial application using Publishing Problem in RC1 - 8.05727.26. I know most would never consider this but our core development is all C++ and so we wanted to leverage 2.0 and the new C++/CLI Language Specification Standard.

All is going well except for one problem. When we Publish our Application and attempt to install it on a fresh machine the wrong 2.0 .NET Framework is installed. First the Published Install detects that there is no .NET 2.0 Framework and begins downloading and installing. What it installs is version v2.0.50215, we need to have v2.0.50727 installed since that is what we are building against.

How can this be corrected???
bxs122
Go in the publish settings, prerequisites , and then click on the .NET Framwork 2.0.
Now select "Download prerequisties from the same location as my application".

Now you are ok.

Giuseppe

Let me know.



Giuseppe Porcelli
Giuseppe Porcelli
Looked for  good thirty minutes ... where is 'publish settings prerequisites' ??
bxs122
click with right mouse on your solution in solution explorer, then click property.
you will see the tab publish.


Giuseppe Porcelli
Giuseppe Porcelli

Thanx ... gave it a try and found that after the publish I needed a new folder/file setup in the setup.exe folder. I downloaded and placed a 2.0.50727.26 version of dotnetfx\dotnetfx.exe  --  installation started on double click of setup.exe but after .NET 2.0 framework install completed I got an error from my application's install. The error is listed below. Bottom line for me at this point is thinking there is no funcitonong Publish capability with RC1. There also appears to be no .NET 2.0 framework you can install that is of a same version level as that you are building against.

PLATFORM VERSION INFO
 Windows    : 5.1.2600.131072 (Win32NT)
 Common Language Runtime  : 2.0.50727.26
 System.Deployment.dll   : 2.0.50727.26 (RTM.050727-2600)
 mscorwks.dll    : 2.0.50727.26 (RTM.050727-2600)
 dfdll.dll    : 2.0.50727.26 (RTM.050727-2600)
 dfshim.dll    : 2.0.50727.26 (RTM.050727-2600)

SOURCES
 Deployment url   : file:///Z:/Display%20&%20Print%20Sample.publish/Display%20&%20Print%20Sample.application

ERROR SUMMARY
 Below is a summary of the errors, details of these errors are listed later in the log.
 * Activation of Z:\Display & Print Sample.publish\Display & Print Sample.application resulted in exception. Following failure messages were detected:
  + Exception reading manifest from file:///Z:/Display%20&%20Print%20Sample.publish/Display%20&%20Print%20Sample.application: the manifest may not be valid or the file could not be opened.
  + Deployment manifest is not semantically valid.
  + Manifest identity has one or more invalid characters: Display & Print Sample.application.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
 No transaction error was detected.

WARNINGS
 There were no warnings during this operation.

OPERATION PROGRESS STATUS
 * [10/23/2005 5:11:39 PM] : Activation of Z:\Display & Print Sample.publish\Display & Print Sample.application has started.

ERROR DETAILS
 Following errors were detected during this operation.
 * [10/23/2005 5:11:40 PM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
  - Exception reading manifest from file:///Z:/Display%20&%20Print%20Sample.publish/Display%20&%20Print%20Sample.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)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
  --- Inner Exception ---
  System.Deployment.Application.InvalidDeploymentException (ManifestSemanticValidation)
  - Deployment manifest is not semantically valid.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemanticsForDeploymentRole()
   at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemantics(ManifestType manifestType)
   at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
  --- Inner Exception ---
  System.Deployment.Application.InvalidDeploymentException (ManifestComponentSemanticValidation)
  - Manifest identity has one or more invalid characters: Display & Print Sample.application.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.Manifest.AssemblyManifest.ValidateAssemblyIdentity(DefinitionIdentity identity)
   at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemanticsForDeploymentRole()

COMPONENT STORE TRANSACTION DETAILS
 No transaction information is available.

 

bxs122
Now the problem is not the Framework 2.0 but the manifest that is not correct.

Open the folder z:\Display & Print Sample.publish\

1) delete all the files in this directory.
2) uninstall the application from client machine
3) rebuild the solution without to do nothing else in your self, only rebuild it.

try now to install on the client machine.

Let me know.





Giuseppe Porcelli
Giuseppe Porcelli
Unfortunately you can have the & character in the deploymentProvider.
You can make this app not available for offline usage (no deploymentProvider in the manifest) and it will work fine
OR
make the directory with out & char like Dispaly and Publish and publish to it.
You will be OK

Sreekanth Bharatham
small correction:
Unfortunately you can NOT have the & character in the deploymentProvider.
Sreekanth Bharatham
reply 8

You can use google to search for other answers

 

More Articles

• Install Wizard problem
• How to edit the application manifest file?
• Activation Key
• Manifest Path limit of 100 characters
• Application Does not show up in add remove programs
• Determine winfx runtime component and version number
• Conditional Dialogs in deployment project
• AppUpdater not working from outside network!
• problem with loading external dll
• Appupdater Woes......
Bookmark and Share
Welcome to Bokebb   New Update  
 

New Articles

• cant auto download third party components?
• VS 2005 Setup Project- Display files dur
• request password before installatio proc
• Error build Setup project if lage file a
• How can I install my program files into
• Send URL querystring from Windows Form
• Urgent - Max Users On Published VB.Net a
• .Net framework 1.1 deployement
• How to Add Assembly file?
• Deploying files not listed in the Publis
• how can i make the embedded control resi
• Click Once with two project !!!
• Resigning problem?
• Deploy Project built in XP won't run on
• SignCode CMD Line nolonger working with

Hot Articles

• Window Application startup position mini
• ClickOnce Signing Problem
• Problems with embedded controls in IE (P
• HTTP Redirect error during clickonce
• Problemas con Crystal Reports
• Outlook application
• How to resize Windows Forms controls on
• How can I deploy an activeX control with
• clickonce error when using clickonce api
• Registry Condition
• Error On Install
• A standard window inside IE
• Embedding a word Window in VB.NET word app
• What do I need to do to deploy controls
• Online ClickOnce deployment

Recommend Articles

• ClickOnce error "Calculating permis
• Deploying a system
• How to access the publish version in the
• How do I install to a custom location on
• ClickOnce executable names
• Writing exe path to registry.
• how to restrict the installation location
• publish.htm missing
• Changing an installation's files after p
• ClickOnce Error When Publishing: PathToo
• Can't Use ClickOnce
• Distributing application to customers?
• param tag does not work!!!
• Running application online
• Application Updater Component / Apache