I have created a program on my Windows XP SP2 Machine using VBEE and I
used ClickOnce to install it to a network share. I have already
installed the dotnet framework on the pc (a Windows 2000 SP4 machine)
and when I ran the install I got an error that the application was
improperly formatted, yet I can install it onto my machine (and another
windows XP SP2 Machine) perfectly. Below are the details. I
am in desperate need of help with this as it is an application that our
accounting department needs asap (and I have put a lot of work
into!). Thank you in advance for your help.
----------------------------------Details-----------------------------------------------
PLATFORM VERSION INFO
Windows : 5.0.2195.262144 (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://accounting/apps/TaxCalc/TAXITE~1.APP
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of
\\accounting\apps\TaxCalc\TAXITE~1.APP resulted in exception. Following
failure messages were detected:
+ Exception reading manifest from
file://accounting/apps/TaxCalc/TAXITE~1.APP: the manifest may not be
valid or the file could not be opened.
+ Manifest XML signature is not valid.
+ The system cannot find the file specified.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [3/15/2006 12:25:39 PM] : Activation of \\accounting\apps\TaxCalc\TAXITE~1.APP has started.
ERROR DETAILS
Following errors were detected during this operation.
* [3/15/2006 12:26:02 PM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from
file://accounting/apps/TaxCalc/TAXITE~1.APP: the manifest may not be
valid or the file could not be opened.
- Source: System.Deployment
- Stack trace:
at
System.Deployment.Application.ManifestReader.FromDocument(String
localPath, ManifestType manifestType, Uri sourceUri)
at
System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore
subStore, Uri& sourceUri, TempFile& tempFile,
SubscriptionState& subState, IDownloadNotification notification,
DownloadOptions options, ServerInformation& serverInformation)
at
System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore
subStore, Uri& sourceUri, TempFile& tempFile,
SubscriptionState& subState, IDownloadNotification notification,
DownloadOptions options)
at
System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri
activationUri, Boolean isShortcut)
at
System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object
state)
--- Inner Exception ---
System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
- Manifest XML signature is not valid.
- Source: System.Deployment
- Stack trace:
at
System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream
s)
at
System.Deployment.Application.ManifestReader.FromDocument(String
localPath, ManifestType manifestType, Uri sourceUri)
--- Inner Exception ---
System.Security.Cryptography.CryptographicException
- The system cannot find the file specified.
- Source: System.Deployment
- Stack trace:
at
System.Deployment.Internal.CodeSigning.SignedCmiManifest.VerifyPublicKeyToken()
at
System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags
verifyFlags)
at
System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream
s)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
ClickOnce Install Problem
Hot Topic
- Adding an Access Connection to Visual J# 2005 Express beta 2
- Playing wave files
- ListView Control
- VB2005 don't view SQL SERVER EXPRESS
- Can not download the express edition
- e.graphics in wrong area.
- print image from resource
- Insert record into a table with an identity column
- Need Autonum feature in VB / SQL Express Table
- Found the solution.. finally
VS Express Editions
- Can't remove .NET Framework 2.0 Beta 1
- problem with sn.exe -k myfirstkey.snk
- Thanks
- Formating of numbers and dates on text data binded controls
- A little trouble installing Visual Studio
- Toolbox: (1)How to bring in all the controls?
- SystemSound versus PlaySound
- Starting to work with Arrays - Two Questions
- Learning -Books-
- Can't start visual C++ Express
ClickOnce Install Problem
Skaale
Hi Lydon
Did you ever manage to solve this issue; I have exactly the same error message/log on one XP box. I would really like to find out how to solve this. Any help would be appreciated.
wizzlestik
Lydon,
I don't understand the error message, but have you installed the redistributable file mentioned here
http://www.microsoft.com/downloads/details.aspx FamilyID=4b6140f9-2d36-4977-8fa1-6f8a0f5dca8f&DisplayLang=en
I'm still learning about these files so I'm not sure if it applies.
Montana
I don't seem to have the executable (mageui.exe) anywhere on my machine. Does it come with the Express Edition
@JacoE,
No, I haven't managed to solve my problem yet. I just placed all of the files from my <project>\Bin\Release directory and placed them on a network drive and created a shortcut for each of the users...
jm2320
One thing I did do though, is I copied my Bin\Release folder to a network share and ran the .exe file from the computer and the application opened like a champ... So, it is working and using it from a network share is not a problem for this particular application, but I still want to know why my stuff doesn't install on windows 2000 machines! Oh well, I guess I'll have to learn something about manifest files... doesn't sound very fun....
MusicMagi
Lydon,
I don't know what's causing your problem. There are many problems; seems like few answers from Microsoft.
The moderator and others have commented that Express was provided for "Hobbyists" and "learners"; perhaps you did not notice that disclaimer I didn't see it, and was expecting something dependable from Microsoft.
So one idea is: Do not utilize Express for a business application.
Don't know if purchased editions are any better.
George
XavierMe
cvayou
mageui.exe is part of the Dotnet Framework 2.0 SDK. If you haven't downloaded it yet(the SDK) you should..............be warned though, it is a 330+Meg download. But, it contains all kinds of tools (including Mageui.exe & mage.exe the command line version) and example code. It is worth the time to download. For dialup , it would be a real pain. But, if you have broadband connection then I really reccommend it. I use Mageui.exe with SharpDevelop's new 2.0 version, Corsavy since it does not come with an installer. From my limited use, it works well.
james
aka:Trucker
Iko
The reason that I am using the Express Edition in the first place is because my employer doesn't see what great things can be done with Visual Studio 2005, and I thought that maybe by creating some good applications I could help them see. But, since it doesn't work correctly, I guess I'm pretty much just killing my argument.
Eric M.
Hey Lydon.
Sounds like it might have to do with the manifest file. I know that when I used VB 6 to program apps for Windows XP I would have to include a .manifest file to allow the app to call and use Windows XP Visual Styles.
It may be that the manifest that is created by VBEE is only for Windows XP.
If you can live without the Visual Styles, you could try disabling them. You can do so by going to the Project menu and selecting your application properties. Then select the APPLICATION tab on the left side. You should see an option that states "Enable XP visual styles"
Make sure that is UNCHECKED. Now rebuild and publish your app (or whatever you were normally doing) and install the new version on your 2000 PC. It should work. I can't guarantee it, but it reads like it is the manifest file. I would try that first. That might get some direction on the issue.
Kawarjit Bedi - MSFT
Something you should keep in mind is to sign the file after changing it. The easiest way to change your manifest file is to open it using the mageui.exe which is installed with your visual studio, it will allow you to save it signed in a easy way.
Steven