.NET Version : 2.0
Visual Studio: 2005

I have run across an error after finishing deploying ClickOnce application to a shared network folder.
It's avaiable "Online" only.

When clicking "Run", application is installed and is present in application cache but displays "Application cannot be started. Contact application vendor".

I have cleared cache using "mage -cc" and also deleted all files under "C:\Documents and Settings\<user name>Local Settings\Apps\2.0".

But I am still getting "Value does not fall within the expected range".

When I read solved thread with this problem, some peopel were able to fix the problem by clearing the cache but it does not work for my case since it is occuring even on a newly built machine.

Anyone has any tips on where I should be looking at?
Thank you in advance.




ERROR DETAILS
Following errors were detected during this operation.
* [11/5/2007 11:11:42 AM] 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)

Unforunately this error can cause due to various reasons. Can you check if you have listed any of your files multiple times in application manifest ? Check files listed under <assembly> and <files> sections.

Unforunately this error can cause due to various reasons. Can you check if you have listed any of your files multiple times in application manifest ? Check files listed under <assembly> and <files> sections.

I do see some "warning" messages that says that there is already a file so cannot add it to the project.

I am in process of removing all the warning signs and see how it will come out.

Thank you, Kunal.

Removing all those warning messages fixed the problem.

I did had to manually delete some of the corrupt portion in ".csproj" files (yes, had to modify 4 cs project files...) and removed all references and re-added the same references.

Since there were only 5 projects in the solution, adding/removing over 100 overlapping references was a pain. but it worked.

BTW, here is the MSDN link to my previous post problem
http://msdn2.microsoft.com/en-us/library/tfszfd6t(vs.80).aspx

And some helpful troubleshooting tips as well
http://msdn2.microsoft.com/en-us/library/ms229001.aspx

Man, I never would have guessed that, project files were corrupt... and had multiple references to the same assembly...