vale_dr

Hi!!

I have got a problem!!

i made a windows application with VB 2005... and i published it with a Test Certificate for ClickOnce.

when i start the installation program it doesn't finish the process and generate this log error... please help me!!!

Thanks Valerio

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:///C:/Documents%20and%20Settings/user/Desktop/setup/pubblicazione%20da%20WJ/WinApp1.application
Application url : file:///C:/Documents%20and%20Settings/user/Desktop/setup/pubblicazione%20da%20WJ/WinApp1_1_2_0_32/WinApp1.exe.manifest

IDENTITIES
Deployment Identity : WinApp1.application, Version=1.2.0.32, Culture=it-IT, PublicKeyToken=f9a99527b18b7645, processorArchitecture=msil
Application Identity : WinApp1.exe, Version=1.2.0.32, Culture=it-IT, PublicKeyToken=f9a99527b18b7645, processorArchitecture=msil, type=win32

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:\Documents and Settings\user\Desktop\setup\pubblicazione da WJ\WinApp1.application resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [12/09/2005 16.12.15] : Activation of C:\Documents and Settings\user\Desktop\setup\pubblicazione da WJ\WinApp1.application has started.
* [12/09/2005 16.12.15] : Processing of deployment manifest has successfully completed.
* [12/09/2005 16.12.15] : Installation of the application has started.
* [12/09/2005 16.12.15] : Processing of application manifest has successfully completed.
* [12/09/2005 16.12.18] : Request of trust and detection of platform is complete.
* [12/09/2005 16.12.20] : Downloading of subscription dependencies is complete.
* [12/09/2005 16.12.20] : Commit of the downloaded application has started.
* [12/09/2005 16.12.25] : Installation of application has successfully completed.

ERROR DETAILS
Following errors were detected during this operation.
* [12/09/2005 16.12.25] System.ArgumentException
- Value does not fall within the expected range.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.NativeMethods.CorLaunchApplication(UInt32 hostType, String applicationFullName, Int32 manifestPathsCount, String[] manifestPaths, Int32 activationDataCount, String[] activationData, PROCESS_INFORMATION processInformation)
at System.Deployment.Application.ComponentStore.ActivateApplication(DefinitionAppId appId, Uri activationUri)
at System.Deployment.Application.SubscriptionStore.ActivateApplication(DefinitionAppId appId, Uri activationUri)
at System.Deployment.Application.ApplicationActivator.Activate(DefinitionAppId appId, AssemblyManifest appManifest, Uri activationUri)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
* Transaction at [12/09/2005 16.12.24]
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: RGZ9EJ71.14C.application
+ System.Deployment.Internal.Isolation.StoreOperationSetDeploymentMetadata
- Status: Set
- HRESULT: 0x0
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: WinApp1.exe.manifest
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: Microsoft.ReportViewer.WinForms.xml
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: Logo Porta.ico
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: WinApp1.xml
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: WinApp1.pdb
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: WinApp1.exe.config
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: Microsoft.ReportViewer.ProcessingObjectModel.dll.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: Microsoft.ReportViewer.ProcessingObjectModel.dll
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: Microsoft.ReportViewer.WinForms.dll.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: Microsoft.ReportViewer.WinForms.dll
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: office.dll.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: office.dll
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: Interop.ShockwaveFlashObjects.dll.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: Interop.ShockwaveFlashObjects.dll
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: ADODB.dll.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: ADODB.dll
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: Microsoft.Vbe.Interop.dll.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: Microsoft.Vbe.Interop.dll
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: Microsoft.Vbe.Interop.Forms.dll.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: Microsoft.Vbe.Interop.Forms.dll
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: Microsoft.StdFormat.dll.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: Microsoft.StdFormat.dll
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: WinApp1.exe.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: WinApp1.exe
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: Microsoft.Office.Interop.Word.dll.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: Microsoft.Office.Interop.Word.dll
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: Microsoft.ReportViewer.Common.dll.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: Microsoft.ReportViewer.Common.dll
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: stdole.dll.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: stdole.dll
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: AxInterop.ShockwaveFlashObjects.dll.genman
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: AxInterop.ShockwaveFlashObjects.dll
+ System.Deployment.Internal.Isolation.StoreOperationInstallDeployment
- Status: Installed
- HRESULT: 0x0
- AppId: file:///C:/Documents%20and%20Settings/user/Desktop/setup/pubblicazione%20da%20WJ/WinApp1.application#WinApp1.application, Version=1.2.0.32, Culture=it-IT, PublicKeyToken=f9a99527b18b7645, processorArchitecture=msil
+ System.Deployment.Internal.Isolation.StoreOperationSetDeploymentMetadata
- Status: Set
- HRESULT: 0x0
+ System.Deployment.Internal.Isolation.StoreTransactionOperationType (27)
- HRESULT: 0x0



Re: Visual Basic IDE problem with publishing

Bruno Yu - MSFT

vale_dr,

According to your error report on ClickOnce using Test Certificate, I would like to provide you the suggestions as follows:

1. Please check your Test Certificate. You can try to create a new Test Certificate. The Create Test Certificate dialog box creates a test certificate to be used for signing your ClickOnce application and deployment manifests. Provide this dialog box with a password for the new strong-name key file.

To access this dialog box, select a project node in Solution Explorer, then on the Project menu, click Properties. When the Project Designer appears, click the Signing tab. On the Signing page, click the Create Test Certificate button.


Then please enter a password for the new strong-name key file for the test certificate. The file is named projectname_TemporaryKey.pfx. If you click OK without typing a password, the .pfx file will not be password encrypted.

2. ClickOnce Deployment and Authenticode

You can store certificates as a .pfx file on your file system, or you can store them inside of a key container. A user on a Windows domain can have a number of key containers. By default, MakeCert.exe will store certificates in your personal key container, unless you specify it should save it to a .pfx instead. Mage.exe and MageUI.exe, the .NET Framework SDK tools for creating ClickOnce deployments, will enable you to use certificates stored in either fashion.

3. You can also try to use ClickOnce manually and the following article shows the way:

Walkthrough: Deploying a ClickOnce Application Manually

If you do not use Visual Studio regularly, need to automate the deployment process, or need to use advanced deployment features such as Trusted Application Deployment, you should use the Mage.exe command-line tool to create your ClickOnce manifests. The following walkthrough takes you through all of the steps required to generate a full ClickOnce deployment using either the command-line version (Mage.exe) or the Windows Forms version (MageUI.exe) of the Manifest Generation and Editing Tool.

Hope that can help you with this kind of problems.






Re: Visual Basic IDE problem with publishing

vale_dr

Thank you very much for the suggestion. when creating a new a new Test Certificate with a password I succeeded to resolve my problem.

vale_dr