No Vista x64 Support

May 16, 2009 at 2:20 PM

Would not install correctly or run:

 

PLATFORM VERSION INFO
 Windows    : 6.0.6002.131072 (Win32NT)
 Common Language Runtime  : 2.0.50727.3074
 System.Deployment.dll   : 2.0.50727.3074 (QFE.050727-3000)
 mscorwks.dll    : 2.0.50727.3074 (QFE.050727-3000)
 dfdll.dll    : 2.0.50727.3074 (QFE.050727-3000)
 dfshim.dll    : 2.0.50727.3074 (QFE.050727-3000)

SOURCES
 Deployment url   : file:///C:/Files/Audio%20&%20Video%20Apps/iWatchSyncer%20v1.0.0.0/iWatchSyncer.application
 Application url   : file:///C:/Files/Audio%20&%20Video%20Apps/iWatchSyncer%20v1.0.0.0/Application%20Files/iWatchSyncer_0_1_0_0/iWatchSyncer.exe.manifest

IDENTITIES
 Deployment Identity  : iWatchSyncer.application, Version=0.1.0.0, Culture=neutral, PublicKeyToken=4995aab1d6a7ffb7, processorArchitecture=msil
 Application Identity  : iWatchSyncer.exe, Version=0.1.0.0, Culture=neutral, PublicKeyToken=4995aab1d6a7ffb7, 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:\Files\Audio & Video Apps\iWatchSyncer v1.0.0.0\iWatchSyncer.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
 * [5/16/2009 8:19:37 AM] : Activation of C:\Files\Audio & Video Apps\iWatchSyncer v1.0.0.0\iWatchSyncer.application has started.
 * [5/16/2009 8:19:40 AM] : Processing of deployment manifest has successfully completed.
 * [5/16/2009 8:19:40 AM] : Installation of the application has started.
 * [5/16/2009 8:19:40 AM] : Processing of application manifest has successfully completed.

ERROR DETAILS
 Following errors were detected during this operation.
 * [5/16/2009 8:19:40 AM] System.ArgumentException
  - Value does not fall within the expected range.
  - Source: mscorlib
  - Stack trace:
   at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
   at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
   at System.Deployment.Application.ActivationDescription.ToActivationContext()
   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)

COMPONENT STORE TRANSACTION DETAILS
 No transaction information is available.

 

May 17, 2009 at 8:45 PM

Not working on Vista x64? That is something I can't test for the moment... I'm only working in Vista x32 and Win XP...

But I'll check the internet for any know issues with x64 and .Net applications.

May 18, 2009 at 12:04 AM

I am a developer myself, and I would be happy to do some testing, if you want me to.

May 18, 2009 at 6:48 AM

laurin, I've found the solution!

It's a known bug of the click once installation procedure... the details are here: http://blogs.msdn.com/gauravb/archive/2008/12/02/clickonce-application-does-not-install-when-the-deployment-path-includes-ampersands.aspx

In short, don't use an & in your installation path.