I'm attempting to deploy my first project using ClickOnce. This
project is being deployed with a setup project, but that is not nearly as convenient
as ClickOnce appears. When I try to publish the project I get an error that I
am unable to locate any solution for, and I don't even have any idea where to
look to begin fixing it. The error sounds very cryptic to me so I'm hoping
someone can point me in the proper direction. The project I'm trying to deploy
is written in C#, although I don't think that matters much. I did create an
empty project and it deploys fine. I've pasted there error below and I would appreciate
anyone who can even give me a place to begin looking for an answer.
Error 36
"Properties\app.manifest;obj\Debug\LUMS.exe.manifest;obj\Release\LUMS.exe.manifest;bin\Release\LUMS.exe.manifest;bin\Release\LUMS.vshost.exe.manifest"
is an invalid value for the "BaseManifest" parameter of the
"GenerateTrustInfo" task. Multiple items cannot be passed into a
parameter of type
"Microsoft.Build.Framework.ITaskItem". LUMS
|
| RobinCS Tuesday, August 29, 2006 8:54 PM |
Hi,
Are you using visual source safe?
If you are using source safe then here is my solution (Might work too if u re not using source safe):
I had the same problem too and I'm using source safe. I manage to solve the problem. Exclude the ApplicationName.Publish folder in the Bin\Debug Folder from the solution.
Build your solution. Solved!!
Hope I could Help.
|
| SEZJUAN Thursday, January 17, 2008 5:32 AM |
I can explain the error and hopefully my explanation will allow anyone seeing this error fix the problem.
The security settings (i.e. the information from the Security Property Page) is stored in a text file included in the project usually called app.manifest. This file can be found under the 'My Project' or 'Properties' node, depending on your project language. The app.manifest is used as a template and information from the app.manifest and the project properties are combined to create the final application and deployment manifests.
Instead of forcing people to use a file call app.manifest for their template, we look for a file with the build action of 'BaseApplicationManifest'. The publish process only expects one template file and can not handle multiple files with the build action of 'BaseApplicationManifest'. To fix this error, make sure Properties\app.manifest is marked with the build action of 'BaseApplicationManifest' and the other LUMS.exe.manifest are not included in the project. |
| Elizabeth Maher - MSFT Thursday, January 17, 2008 5:40 PM |
Did you find an answer for this? I searched VS help and came back with nothing. I searched the web and this was the only page found.
Thanks,
Lodlaiden |
| lodlaiden Tuesday, December 19, 2006 5:10 PM |
delete the application_name.exe.manifest file from debug folder and compile again
|
| rahou Tuesday, June 05, 2007 3:44 PM |
Hi,
i didthe same thing still it is not working. i deleted wholebin\debug directory and tried to compile the project i got the same error. can some help me to get out of this problem?
Regards
Sriram
|
| SriramKNV Monday, November 26, 2007 6:25 PM |
Did anyone ever figure this out? Still recieving it on my ClickOnce deploy
|
| WinstonSmith007 Wednesday, December 19, 2007 11:10 PM |
Hi,
Are you using visual source safe?
If you are using source safe then here is my solution (Might work too if u re not using source safe):
I had the same problem too and I'm using source safe. I manage to solve the problem. Exclude the ApplicationName.Publish folder in the Bin\Debug Folder from the solution.
Build your solution. Solved!!
Hope I could Help.
|
| SEZJUAN Thursday, January 17, 2008 5:32 AM |
I can explain the error and hopefully my explanation will allow anyone seeing this error fix the problem.
The security settings (i.e. the information from the Security Property Page) is stored in a text file included in the project usually called app.manifest. This file can be found under the 'My Project' or 'Properties' node, depending on your project language. The app.manifest is used as a template and information from the app.manifest and the project properties are combined to create the final application and deployment manifests.
Instead of forcing people to use a file call app.manifest for their template, we look for a file with the build action of 'BaseApplicationManifest'. The publish process only expects one template file and can not handle multiple files with the build action of 'BaseApplicationManifest'. To fix this error, make sure Properties\app.manifest is marked with the build action of 'BaseApplicationManifest' and the other LUMS.exe.manifest are not included in the project. |
| Elizabeth Maher - MSFT Thursday, January 17, 2008 5:40 PM |
yes ,you are right ! i meet the same problem |
| Zongxian Friday, July 31, 2009 9:30 AM |