Publishing and installing Windows apps

[Mike P]

Last week I wrote a windows app, published it and then installed it on
my local machine. It all worked perfectly. Now today when I try to run
the app from my Start menu I get the error 'Application cannot be
started. Contact the application vendor'. So I have tried to uninstall
and re-install the app, but when I try to uninstall the app nothing
happens.

Can anybody help with this?

 

[Aneesh P]

Last week I wrote a windows app, published it and then installed it on
my local machine. It all worked perfectly. Now today when I try to run
the app from my Start menu I get the error 'Application cannot be
started. Contact the application vendor'. So I have tried to uninstall
and re-install the app, but when I try to uninstall the app nothing
happens.

Can anybody help with this?

*** Sent via Developersdexhttp://www.developersdex.com***

Are you using .Net setup project?..

 

[Mike P]

All I am doing is building and then publishing my app, and then
installing it from http://localhost/appname/publish.htm. On previous
versions this has worked fine, and on Friday it was working fine on this
version of the app too. I am only getting this error now. Here are the
details of the error :

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

SOURCES
Deployment url :
file:///C:/Documents%20and%20Settings/michaelp/Start%20Menu/Programs/Out
lookInboxArchiver/OutlookInboxArchiver.appref-ms

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\michaelp\Start
Menu\Programs\OutlookInboxArchiver\OutlookInboxArchiver.appref-ms
resulted in exception. Following failure messages were detected:
+ The referenced assembly is not installed on your system. (Exception
from HRESULT: 0x800736B3)

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [04/06/2007 10:35:57] : Activation of C:\Documents and
Settings\michaelp\Start
Menu\Programs\OutlookInboxArchiver\OutlookInboxArchiver.appref-ms has
started.

ERROR DETAILS
Following errors were detected during this operation.
* [04/06/2007 10:35:57] System.Runtime.InteropServices.COMException
- The referenced assembly is not installed on your system. (Exception
from HRESULT: 0x800736B3)
- Source: System.Deployment
- Stack trace:
at
System.Deployment.Internal.Isolation.IStore.GetAssemblyInformation(UInt3
2 Flags, IDefinitionIdentity DefinitionIdentity, Guid& riid)
at
System.Deployment.Internal.Isolation.Store.GetAssemblyManifest(UInt32
Flags, IDefinitionIdentity DefinitionIdentity)
at
System.Deployment.Application.ComponentStore.GetSubscriptionStateInterna
l(DefinitionIdentity subId)
at
System.Deployment.Application.SubscriptionStore.GetSubscriptionStateInte
rnal(SubscriptionState subState)
at
System.Deployment.Application.ApplicationActivator.ProcessOrFollowShortc
ut(String shortcutFile, TempFile& deployFile)
at
System.Deployment.Application.ApplicationActivator.PerformDeploymentActi
vation(Uri activationUri, Boolean isShortcut)
at
System.Deployment.Application.ApplicationActivator.ActivateDeploymentWor
ker(Object state)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

 

[Peter Duniho]

All I am doing is building and then publishing my app, and then
installing it from http://localhost/appname/publish.htm. On previous
versions this has worked fine, and on Friday it was working fine on this
version of the app too. I am only getting this error now. Here are the
details of the error : [...]

Well...what assembly is missing? Can you find it manually? If so, can
you determine whether it's really the assembly being looked for (correct
version and all)? If not, can you determine why it's not being put where
you think your installer should put it?

Pete