Hello, originally posted this in the VB General forum - didn't get much response, so I thought I would post it here. I'm trying to deploy a ClickOnce Windows app. I have successfully installed it in the past. I made some changes to the .mdf file I have referenced in my application (I made the changes in SQL Server). When I published the app on another machine, I started receiving the error message "File ....mdf, has a different computed hash than specified in manifest". I tried a number of different suggestions that people have made on these forums, but no luck - I tried building the app twice, then deploying; I tried manually updating the revision number; I tried creating a new Test Certificate; I tried signing the assembly; I tried making a change to the .mdf file from within the app, and re-publishing; etc. Can someone please assist? We have a client install coming up very soon, so I need to get this resolved as soon as possible. Thanks in advance.

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:///E:/Install/NewDueDiligence.application
Application url: file:///E:/Install/NewDueDiligence_1_0_1_78/NewDueDiligence.exe.manifest

IDENTITIES
Deployment Identity: NewDueDiligence.application, Version=1.0.1.78, Culture=neutral, PublicKeyToken=c153f4632af735c0, processorArchitecture=msil
Application Identity: NewDueDiligence.exe, Version=1.0.1.78, Culture=neutral, PublicKeyToken=c153f4632af735c0, 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 E:\Install\NewDueDiligence.application resulted in exception. Following failure messages were detected:
+ File, DueDiligence.mdf, has a different computed hash than specified in manifest.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [10/23/2006 10:08:58 PM] : Activation of E:\Install\NewDueDiligence.application has started.
* [10/23/2006 10:08:59 PM] : Processing of deployment manifest has successfully completed.
* [10/23/2006 10:08:59 PM] : Installation of the application has started.
* [10/23/2006 10:08:59 PM] : Processing of application manifest has successfully completed.
* [10/23/2006 10:09:01 PM] : Request of trust and detection of platform is complete.

ERROR DETAILS
Following errors were detected during this operation.
* [10/23/2006 10:09:07 PM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
- File, DueDiligence.mdf, has a different computed hash than specified in manifest.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
at System.Deployment.Application.ComponentVerifier.FileComponent.Verify()
at System.Deployment.Application.ComponentVerifier.VerifyComponents()
at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
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)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Actually, the problem was with the manifest itself rather than a file it.

I solved the problem in a different way - Rather than attempting to change the manifest to include additional files, I regenerate the entire clickonce deployment folder each time.

Apparently modifying the manifest through the mageui tool does not always recompute the hash for the manifest.

You can use Mage.exe to regenerate the application manifest. The following link will giveyou some details on how to use it.

http://msdn2.microsoft.com/en-us/library/acz3y3te.aspx

So I'd be trying to figure out why the file is getting changed post publishing. Once you publish your app, you shouldn't generally change the files on the server. If you have a good reason to change them, then you will need to update the manifests using mage.exe as has been suggested.

Any ideas what's changing and why?

It's hard to troubleshoot this without looking at the actual .mdf file and .exe.manifest file. If the file is not being changed post publish there really should not be any reason for hash mismatch especially if installed from local machine. (If this was a web download over http there could be web server or proxy server causing file to be changed somehow but this won't happen in the local machine install case).

Here are few things I'd suggest checking:

(1) Run standalone tool to generate hash of file and compare that with hash in manifest. Attached sample code snippet below that you can compile into a GenerateFileHash.exe tool to spit out the hash of a file. Run it against the .mdf file in published location and compare result with the hash in the app manifest (.exe.manifest file). In the app manifest search for .mdf file and look for hash section under it (e.g. <dsig:DigestValue>ddK2+W5PklMmYt3ordxQjb4BQuA=</dsig:DigestValue>). If the two hashes don't match that would explain the ClickOnce failure.

(2) Does this happen for this one app and one file only? If you remove this one file from the app does install then succeed?

(3) Can you try installing this app on another machine? Do you get the same error?

If you post back with findings from trying this out we can then look into next steps for troubleshooting.

Regards,
Sameer

Sample code for GenerateFileHas.exe tool:

using System;
using System.Security.Cryptography;
using System.IO;

namespace FileHashSample
{
    public class FileHash
    {
        public FileHash()
        {
            return;
        }

        public string ComputeHash(string filePath)
        {
            string filePathNormalized = System.IO.Path.GetFullPath(filePath);
            SHA1 sha = new SHA1Managed();
            FileStream fs = new FileStream(filePathNormalized, FileMode.Open, FileAccess.Read);
            byte[] byteHash = sha.ComputeHash(fs);
            fs.Close();
            return Convert.ToBase64String(byteHash, 0, byteHash.Length);
        }

        public static void Main(string[] args)
        {
            if (args.Length == 0)
            {
                Console.WriteLine("Please Enter a File Path");
                return;
            }
            string filePath = System.IO.Path.GetFullPath(args[0]);
            FileHash objFileHash = new FileHash();
            Console.WriteLine("File Path is {0}", filePath);
            Console.WriteLine("File Hash is {0}", objFileHash.ComputeHash(filePath));
            return;
        }
    }

}

Hi Sameer,

I am facing a similar problem but not in the exact same fashion. The application has been published to a machine and i am able to launch the application on 3 machines and on 2 machines it fails giving a similar error. The error is pasted below. Also, the download of the application does complete on one of the machiens where it is failing, but i dont know where these files get downloaded temporarily. I am assuming that the files somehow get modified in between and want to generate a hash of the files on the machines where its not working, but since i dont know where the file gets downloaded temporarily, so i cant generate the hash. Please suggest a way out.

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   : 
      Server  : Microsoft-IIS/5.0
      X-Powered-By : ASP.NET
 Application url   : 
      Server  : Microsoft-IIS/5.0
      X-Powered-By : ASP.NET

IDENTITIES
 Deployment Identity  : testapp.application, Version=1.0.0.0, Culture=neutral, PublicKeyToken=85225c624ac37fea, processorArchitecture=msil
 Application Identity  : testapp.exe, Version=1.0.0.0, Culture=neutral, PublicKeyToken=85225c624ac37fea, processorArchitecture=msil, type=win32

APPLICATION SUMMARY
 * Online only application.
 * Trust url parameter is set.
ERROR SUMMARY
 Below is a summary of the errors, details of these errors are listed later in the log.
 * Activation of xxx resulted in exception. Following failure messages were detected:
  + File, testapp - xxx.exe, has a different computed hash than specified in manifest.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
 No transaction error was detected.

WARNINGS
 There were no warnings during this operation.

OPERATION PROGRESS STATUS
 * [20/12/2006 05:19:18] : Activation of  has started.
 * [20/12/2006 05:19:18] : Processing of deployment manifest has successfully completed.
 * [20/12/2006 05:19:18] : Installation of the application has started.
 * [20/12/2006 05:19:19] : Processing of application manifest has successfully completed.
 * [20/12/2006 05:19:22] : Request of trust and detection of platform is complete.

ERROR DETAILS
 Following errors were detected during this operation.
 * [20/12/2006 05:19:33] System.Deployment.Application.InvalidDeploymentException (HashValidation)
  - File, testapp - xxx.exe, has a different computed hash than specified in manifest.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
   at System.Deployment.Application.ComponentVerifier.FileComponent.Verify()
   at System.Deployment.Application.ComponentVerifier.VerifyComponents()
   at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
   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)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
 No transaction information is available.

I have been trying to use ClickOnce to deploy a simple WinForms application and have run into similar problems to those described here and some different ones.

Running MageUI.exeto regenerate the hash codesand re-sign the manifest seems to work, although I still get failures on the simplest cases for no apparent reasons.

My caseis not even on a redeploy or update- just regenerating the application and creating a new version can be problemmatic.

What I am trying to do that does not seem to work is to deploy a list of data files containing gif and wav files in the same directory as the executable.

Often after manually adding the list of data files and regeneratingthe hash code and signing the manifestI get errors.

I do not know why is this manual step is even necessary - they are in the project but are not getting deployed.

Even when the deployment does not create errors, the data files are never deployed when the setup.exe is clicked (all local testing, no network).

I have looked at the ApplicationDeployment class at runtime, and everything seems correct, but nothing is copied to the Data directory.

I have tried both types of deployment - the Online only and the Online/Offline that registers the program.

Can anyone provide help for this type of problem? It seems relatively common.

I have more information on the problems with ClickOnce, but no real solutions - hopefully someone else can explain what is happening and provide ideas for getting around the errors.

I tried a local ClickOnce - I created a simple single executable, single DLL solution, published it, and the executable ran, although incorrectly since it requires a number of other files in the same directory.

I tried adding a number of files to the application directory and to the manifest with mageui.exe, rehashed and resigned it, and it got the usual error about the computed hash.

I repeated the same operation (republish, readd files, recalculate hash, re-sign, etc.)and this time the executable ran, although incorrectly because of the missing files. Using procmon to watch which files were being created, the temporary Data directory was created, but the files are never copied to it.

I tried executing the same ClickOnce application project from another computer on the local network in the same domain, and it failed, even if I copied the setup.exe and application directory to the other computer. The interesting point is how it failed - Application manifest has either a different computed hash than the one specified or no hash specified at all.

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:///Q:/temp/ControlPanel/ControlPanel.application
Application url: file:///Q:/temp/ControlPanel/ControlPanel_1_0_0_12/ControlPanel.exe.manifest

IDENTITIES
Deployment Identity: ControlPanel.application, Version=1.0.0.12, Culture=neutral, PublicKeyToken=6826da00991f9aa5, processorArchitecture=msil

APPLICATION SUMMARY
* Online only application.

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of Q:\temp\ControlPanel\ControlPanel.application resulted in exception. Following failure messages were detected:
+ Application manifest has either a different computed hash than the one specified or no hash specified at all.
+ File, ControlPanel.exe.manifest, has a different computed hash than specified in manifest.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [12/27/2006 22:11:49] : Activation of Q:\temp\ControlPanel\ControlPanel.application has started.
* [12/27/2006 22:11:53] : Processing of deployment manifest has successfully completed.
* [12/27/2006 22:11:53] : Installation of the application has started.

ERROR DETAILS
Following errors were detected during this operation.
* [12/27/2006 22:11:53] System.Deployment.Application.InvalidDeploymentException (HashValidation)
- Application manifest has either a different computed hash than the one specified or no hash specified at all.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.DownloadManager.DownloadApplicationManifest(AssemblyManifest deploymentManifest, String targetDir, Uri deploymentUri, IDownloadNotification notification, DownloadOptions options, Uri& appSourceUri, String& appManifestPath)
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)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.Deployment.Application.InvalidDeploymentException (HashValidation)
- File, ControlPanel.exe.manifest, has a different computed hash than specified in manifest.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
at System.Deployment.Application.DownloadManager.DownloadApplicationManifest(AssemblyManifest deploymentManifest, String targetDir, Uri deploymentUri, IDownloadNotification notification, DownloadOptions options, Uri& appSourceUri, String& appManifestPath)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

I got the same error:

"File, AssemblyCode.dll, has a different computed hash than specified in manifest."

where "AssemblyCode.dll" was a library referenced in my EXE that was being deployed. I simply had to remove the reference and add the reference, then re-publish the project. It worked. There seems to be some value that gets changed in the project but perhaps an old value is used when publishing files...

Anyway, remove and add the reference may help you with the mdb file hash problem...

If this helps, please mark this post as the solution...

Thanks

Actually, the problem was with the manifest itself rather than a file it.

I solved the problem in a different way - Rather than attempting to change the manifest to include additional files, I regenerate the entire clickonce deployment folder each time.

Apparently modifying the manifest through the mageui tool does not always recompute the hash for the manifest.

here is another issue,

if you switch from debug to relase or vice varsa, you will get the Hash failure error no matter where you publish

I had the same problem and I solved it using Mage.exe / MageUI.exe

What you need to do is:

- Open the xxx.exe.manifest file using MageUI, select on file on the left pane and populate the necessary files once again and save the manifest singing a key

- Open the base application manifest file using MageUI again and click on application references > Select Manifest and select the manifest you edited in the previous step, save your work and that's it...now the file will have a new hash computed..

Hi all,

I have had this issue for a very long time. I read all you contributed, however, I am a simple man and I would like to see a simple solution. After all, why should I be needing something like Mage to solve what VS2005 and ClickOnce should take care of.

All I am doing is deploying my code over the internal network of our small company. The publishing always workes without issues, but when I want to update the software on client machines I often get this hash difference error message. What I usually then do is simply regenerate (AGAIN!) the whole project and publish again. Trying to update on the client machine then usually works.

However, I simple get mad at having to do everything TWICE all the time!

As stated by other people, this seems to be a fairly common problem. Has no one yet found a proper final solution for this issue. What does Microsoft say to this?

Any feedback is greatly appreciated!

Kind regards,

Marc

I have arrived at a simple (although probably not condoned by Microsoft) solution to this problem. Before you publish a new version, open the target folder and delete (or rename) the folder(s) for the previous version(s) as well as any file with the extension .manifest. This forces .NET to recreate the entire publish package. It may not be pretty, but it works!

Hi there,

Exactly the same experience here. However, it only started to happen when I added a new .resx file to the project for the second language that I need to support. After playing around with it a few hours, I figured that if I also add the .resx file to the Resources of the project, I don't get the above mentioned having-to-publish-twice behaviour any more.

This might help others as well. I do realize, however, this is not the solution, it's just a workaround. At least one has to do this only once...

my 0.02USD

Hi there,

I've been fighting with this for a while myself.

The biggest challenge we're facing now, is that the updating of the manifest needs to be scriptable (i.e. not using mageui)

(Our specificscenario described in more detail at http://russellrockliff.spaces.live.com)

So, I've found the following mage commands sorted us out...

REM Set the working directory

I solved this problem with an .sdf file by:

Manually setting app version greater then the last one.

Uninstalling the one on the development machine.

Removing the sdf from the project then re adding it (creates new dataset thing).

Deleting the VS 2008 project folder/Properties/DataSources/System.Data.DataSet.datasource file.

When I tried publishing it it ran first time.

I only recommend this as a last resort though.

I solved it by removing the offending file (in this case Scripting.dll) and re-referencing it. The reason, I suspect, why it had caused the problem is that I had pinched it from another project.

I too am getting this message with no resolution.

I have tried every solution on the net, and still no luck? I upgraded my laptop to a larger hard drive, and my application
will not update/install on only "SOME" machines. This is hair pulling. Doesn't anyone at Microsoft have a solution to this
or a workaround? There are so many posts on this. I don't want to abandon click once.
See below: Same 'has a different computed hash than specified in manifest.' message that others in this thread are seeing.

MageUI didn't work, creating test certificate didn't work(rebuild all, republish) and many other solutions. I haven't been stumped like this since they change Coke Classic to the ____ flavor years ago....

====================

PLATFORM VERSION INFO
Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.3053
System.Deployment.dll : 2.0.50727.3053 (netfxsp.050727-3000)
mscorwks.dll : 2.0.50727.3053 (netfxsp.050727-3000)
dfdll.dll : 2.0.50727.3053 (netfxsp.050727-3000)
dfshim.dll : 2.0.50727.3053 (netfxsp.050727-3000)

SOURCES
Deployment url: http://craigslistautoposter.southcoastsbs.com/admaker.application.php
Server: Apache/1.3.41 (Unix) PHP/4.4.8 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_ssl/2.8.31 OpenSSL/0.9.7a
X-Powered-By: PHP/4.4.8
Deployment Provider url: http://craigslistautoposter.southcoastsbs.com/admaker.application
Server: Apache/1.3.41 (Unix) PHP/4.4.8 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_ssl/2.8.31 OpenSSL/0.9.7a
Application url: http://craigslistautoposter.southcoastsbs.com/Application%20Files/admaker_2_1_1_18/admaker.exe.manifest
Server: Apache/1.3.41 (Unix) PHP/4.4.8 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_ssl/2.8.31 OpenSSL/0.9.7a

IDENTITIES
Deployment Identity: admaker.application, Version=2.1.1.18, Culture=neutral, PublicKeyToken=5e5a14cb945e4d03, processorArchitecture=msil
Application Identity: admaker.exe, Version=2.1.1.18, Culture=neutral, PublicKeyToken=5e5a14cb945e4d03, 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 http://craigslistautoposter.southcoastsbs.com/admaker.application.php resulted in exception. Following failure messages were detected:
+ File, localpicsII.xml, has a different computed hash than specified in manifest.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [5/1/2009 3:14:56 PM] : Activation of http://craigslistautoposter.southcoastsbs.com/admaker.application.php has started.
* [5/1/2009 3:14:58 PM] : Processing of deployment manifest has successfully completed.
* [5/1/2009 3:14:58 PM] : Installation of the application has started.
* [5/1/2009 3:14:58 PM] : Processing of application manifest has successfully completed.
* [5/1/2009 3:14:59 PM] : Request of trust and detection of platform is complete.

ERROR DETAILS
Following errors were detected during this operation.
* [5/1/2009 3:15:15 PM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
- File, localpicsII.xml, has a different computed hash than specified in manifest.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
at System.Deployment.Application.ComponentVerifier.FileComponent.Verify()
at System.Deployment.Application.ComponentVerifier.VerifyComponents()
at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
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.

Why does your application file have a file extension of ".php" appended to it? Are you changing this after moving it out to your server? This is probably your problem. You can not modify any of the files w/o re-signing the deployment. Additionally, the file association in Windows is set up for .application, and probably isn't opening it the right way if you change it to .php.

RobinDotNet

The filename extension is not necessary for any browser to work. If IE is opening the application file and showing XML, it means you do not have the MIME types set up on your server and this is not serving up the files correctly. Change your MIME types and stop renaming the dang files, and try it again. Here are the MIME types:

These are the MIME types you need in order to host a ClickOnce application:

.application --> application/x-ms-application
.manifest --> application/x-ms-application
.deploy --> application/octet stream

If you are deploying .Net 3.5 as a prerequisite, you need these as well:

.msp --> application/microsoftpatch
.msu --> application/microsoftupdate

If you have vsto apps, you need this one:

.vsto --> application/x-ms-vsto

RobinDotNet