so, what I am trying to say is that if your application is dotnet 2.0 and can be opened with vs 2005 then maybe by setting this compilation parameter to x64, you compile and try again your installation.
in this setting and in visual studio 2005, you can set your application to "x64".
The best way to go is make test in both computers and you will see the pro and cons, sorry there is not cook receipt for this.
ERROR DETAILS Following errors were detected during this operation.
for the future, maybe upgrade from vs 2005 ( which is dotnet 2.0 ) to vs 2010, but then with dotnet framework 4.0 as this app's platform.
in this way, you will have two versions of your application in dotnet 2.0 ( the current one and one x64).
Down load Deployment Manifest Direct(Subscription Store sub Store, Uri& source Uri, Temp File& temp File, IDownload Notification notification, Download Options options, Server Information& server Information) at System.
Foll ow Deployment Provider Uri(Subscription Store sub Store, Assembly Manifest& deployment, Uri& source Uri, Temp File& temp File, IDownload Notification notification, Download Options options) --- Inner Exception --- System. NET application a few years ago before I knew anything about 64-bit OS. NET application that I had built and placed out on our Intranet site using Click Once Deploy; however, it will not install on my 64-bit OS and I get the following message: "Cannot Start Application - Cannot continue. Contact the application vendor for assistance." When I click on the Details button, I get the following: PLATFORM VERSION INFO Windows : 6.1.7600.0 (Win32NT) Common Language Runtime : 4.0.30319.239 System. Down load Deployment Manifest Bypass(Subscription Store sub Store, Uri& source Uri, Temp File& temp File, Subscription State& sub State, IDownload Notification notification, Download Options options) at System.