Hi,

We are working on a Samrt Client project which uses Composite Applciation UI block.
We need to deploy our app using ClickOnce deployment. The Dll's attached with Shell.exe are getting published using VS 2008 and are installed properly. We need to add our project Dll's and some XML files to be deployed.
We are using MageUI.exe . Which gives us the error

Warning MSB3110: Assembly 'C:\ms1DeployClickOnce\Application Files\Shell_1_0_0_14\Shell.application.deploy' has mismatched identity 'Shell.application', expected file name: Shell.application.application'.


while we click the 'Save' button.

Does any body face this problem. How to resolve this issue.

Hi We_are_one,

Please check out this thread , and see if the methods discussed there can solve your problem.

If the problem can't be solved, please feel free to let me know.

Best regards,
Bruce Zhou

---

Please mark the replies as answers if they help and unmark if they don't.

Hi We_are_one,

Please check out this thread , and see if the methods discussed there can solve your problem.

If the problem can't be solved, please feel free to let me know.

Best regards,
Bruce Zhou

---

Please mark the replies as answers if they help and unmark if they don't.

Hi We_are_one,

How's your problem now? If the problem can't be solved, please do reply back with latest information.

Best regards,
Bruce Zhou

---

Please mark the replies as answers if they help and unmark if they don't.

I have a similar problem (VS2008 3.5 deploy) adding in a folder. As the instructions indicate, (http://msdn.microsoft.com/en-us/library/xc3tc5xx.aspx), copy the files to the version subdirectory and include the extra data files. In this case, these are encrypted data files located in a sub-folder.

After completing steps 5,6,7,8,9, 10, 11, and 12, the save as dialog brings up the message listed by We_are_one.

"Warning MSB3110: Assembly '\\MyServerName\myCustomApplicationName\Application Files\myChosenApplicationName_1_0_0_6\myCustomApplicationName.application' has mismatched identity 'myChosenApplicationName.application', expected file name: 'myCustomApplicationName.application.application'."

There is a choice given the warning above that says would you like to continue. Clicking YES provides two options - {Signing Options - app1exe.manifest} which is to sign the certificate file by choosing a signing file from the folder, use the previous, or create a new signing file (pfx file). Choosing the previous signing file gives the message above.

I copied down the original (temporary) pfx file that had been created by the last installation. Using this file, I was able to sign the newly created version. (Step 13 - apparently the option to sign with stored certificate is not functioning when adding extraneous data files)

Followed the remaining steps. It gets a bit confusing here because now that the new application (version) files have been created, clicking on the setup button still attempts to access the prvious version of the setup file. Still have that to figure out.

Incidentally, I think the problem above may have been due to the user not clicking save as. If save is hit, the application extenstion seems to become "application.application"

My Log File indicates that going up only one level for the folder may not have been correct but switching the files did not change this error:

PLATFORM VERSION INFO
Windows : 6.1.7600.0 (Win32NT)
Common Language Runtime : 2.0.50727.4927
System.Deployment.dll : 2.0.50727.4927 (NetFXspW7.050727-4900)
mscorwks.dll : 2.0.50727.4927 (NetFXspW7.050727-4900)
dfdll.dll : 2.0.50727.4927 (NetFXspW7.050727-4900)
dfshim.dll : 2.0.50727.4927 (NetFXspW7.050727-4900)

SOURCES
Deployment url: file://myServer/myCustomApplication/myCustomApplication.application
Deployment Provider url: file://myServer/myCustomApplication/myCustomApplication.application

IDENTITIES
Deployment Identity: myCustomApplication.app, Version=1.0.0.6, Culture=neutral, PublicKeyToken=ac6315e3efd4a7b2, processorArchitecture=msil

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 \\myServer\myCustomApplication\myCustomApplication.application resulted in exception. Following failure messages were detected:
+ Downloading file://myServer/myCustomApplication/myCustomApplication_1_0_0_6/myCustomApplication.exe.manifest did not succeed.
+ Could not find a part of the path '\\myServer\myCustomApplication\myCustomApplication_1_0_0_6\myCustomApplication.exe.manifest'.
+ Could not find a part of the path '\\myServer\myCustomApplication\myCustomApplication_1_0_0_6\myCustomApplication.exe.manifest'.
+ Could not find a part of the path '\\myServer\myCustomApplication\myCustomApplication_1_0_0_6\myCustomApplication.exe.manifest'.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [9/4/2009 10:20:45 AM] : Activation of \\myServer\myCustomApplication\myCustomApplication.application has started.
* [9/4/2009 10:20:46 AM] : Processing of deployment manifest has successfully completed.
* [9/4/2009 10:20:46 AM] : Installation of the application has started.

ERROR DETAILS
Following errors were detected during this operation.
* [9/4/2009 10:20:46 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading file://myServer/myCustomApplication/myCustomApplication_1_0_0_6/myCustomApplication.exe.manifest did not succeed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadApplicationManifest(AssemblyManifest deploymentManifest, String targetDir, Uri deploymentUri, IDownloadNotification notification, DownloadOptions options, Uri& appSourceUri, String& appManifestPath)
at System.Deployment.Application.DownloadManager.DownloadApplicationManifest(AssemblyManifest deploymentManifest, String targetDir, Uri deploymentUri, 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, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.Net.WebException
- Could not find a part of the path '\\myServer\myCustomApplication\myCustomApplication_1_0_0_6\myCustomApplication.exe.manifest'.
- Source: System
- Stack trace:
at System.Net.FileWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.FileWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
--- Inner Exception ---
System.Net.WebException
- Could not find a part of the path '\\myServer\myCustomApplication\myCustomApplication_1_0_0_6\myCustomApplication.exe.manifest'.
- Source: System
- Stack trace:
at System.Net.FileWebResponse..ctor(FileWebRequest request, Uri uri, FileAccess access, Boolean asyncHint)
at System.Net.FileWebRequest.GetResponseCallback(Object state)
--- Inner Exception ---
System.IO.DirectoryNotFoundException
- Could not find a part of the path '\\myServer\myCustomApplication\myCustomApplication_1_0_0_6\myCustomApplication.exe.manifest'.
- Source: mscorlib
- Stack trace:
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean useAsync)
at System.Net.FileWebStream..ctor(FileWebRequest request, String path, FileMode mode, FileAccess access, FileShare sharing, Int32 length, Boolean async)
at System.Net.FileWebResponse..ctor(FileWebRequest request, Uri uri, FileAccess access, Boolean asyncHint)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Actually found this whole process was much simpler than originally thought (MageUI tool aside). Focus should have been to get it running locally rather than on a network share somewhere because once it is local, just making a copy of the folder and moving it to the server as a virtual share solved all the problems. The security issues above resolved because the credentials were not in question on the local machine.