When I publish my application everything goes fine, I put it on my harddrive/website/desktop.
But when I try to run it I get this error:
This application is improperly formatted
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 : http://localhost/Publish/Appointment.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://localhost/Publish/Appointment.application resulted in exception. Following failure messages were detected:
+ Exception reading manifest from http://localhost/Publish/Appointment.application: the manifest may not be valid or the file could not be opened.
+ Deployment manifest is not semantically valid.
+ Application reference identity must be strongly named.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [8/03/2006 17:22:07] : Activation of http://localhost/Publish/Appointment.application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [8/03/2006 17:22:07] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from http://localhost/Publish/Appointment.application: 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 (ManifestSemanticValidation)
- Deployment manifest is not semantically valid.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemanticsForDeploymentRole()
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemantics(ManifestType manifestType)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
--- Inner Exception ---
System.Deployment.Application.InvalidDeploymentException (ManifestComponentSemanticValidation)
- Application reference identity must be strongly named.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateApplicationDependency(DependentAssembly da)
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemanticsForDeploymentRole()
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
Anyone knows why I get this :S
Regards,
Gijs Vos

publishing outlook add-in
InfoDOG
Gijs,
Please take a look at MSDN help documentation about deploying outlook add-ins.
http://msdn2.microsoft.com/en-us/library/ms269007.aspx
It is very detailed and addresses the questions you have - about registry entries specifically look at the "Note" section that contains the information:
The Publish Wizard does not create the registry entries required to run the add-in. If you use the Publish Wizard to deploy an add-in, you must create these registry entries yourself, for example, by using a registry (.reg) file. The Publish Wizard also does not overwrite or remove the registry entries that are created on the development computer when you build your project. For more information about building projects, see Office Solution Build Process Overview. For more information about the registry entries required to run Outlook add-ins, see "Required Registry Entries" in this topic.
Thanks.
Zeeshan Anwer Khatri
You can find four deployment scenarios at http://blogs.msdn.com/vsto2
Depending on your situation you should be able to select one of the four scenarios to implement your CAS security the right way.
-= Maarten =-
KhurramAziz
Yes I use the publish function to put it on my hdd, I've also tried a website.
However I didn't add the registry keys I guess, but does that mean it can't install it also/same with the security policies or smt :S
Regards,
Gijs Vos
Christopher11
Ok I got so far that I can get it installed, the problem left is the CAS security policy, any decent tutorials on it on the web MSDN didn't help me much :S also I don't know much about it, this is the last error left :)
Could not load file or assembly 'Appointment, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Failed to grant permission to execute. (Exception from HRESULT: 0x80131418)
Thx for your help so far.
Regards,
Gijs Vos
Genival Carvalho
Gijs,
I'll try and find someone who can take a look at this. In the meantime have you read the following:
http://msdn2.microsoft.com/en-us/library/ms269007.aspx
It may help. Is this how you're publishing your addin
Ade
tkrasinger
< xml version="1.0" encoding="utf-8" >
<asmv1:assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd" manifestVersion="1.0" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns="urn:schemas-microsoft-com:asm.v2" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:xrml="urn:mpeg:mpeg21:2003:01-REL-R-NS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<assemblyIdentity name="Appointment.application" version="1.0.0.5" publicKeyToken="0000000000000000" language="neutral" processorArchitecture="msil" xmlns="urn:schemas-microsoft-com:asm.v1" />
<description asmv2:publisher="Appointment" asmv2:product="Appointment" xmlns="urn:schemas-microsoft-com:asm.v1" />
<deployment install="true" />
<dependency>
<dependentAssembly dependencyType="install" codebase="Appointment_1.0.0.5\Appointment.dll.manifest" size="743">
<assemblyIdentity name="Appointment.dll" version="1.0.0.5" />
<hash>
<dsig:Transforms>
<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<dsig:DigestValue>ecAy+BcXNWFPhW09USsgStRy7uA=</dsig:DigestValue>
</hash>
</dependentAssembly>
</dependency>
</asmv1:assembly>
I hope this was what you need :S
Regards,
Gijs Vos
AlexandruS
Gijs,
So it would seem like the application manifest is malformed. Could you post its contents also
Thanks,
Ade