I think I might have found the solution to the problem.
It was because the solotion was converted from a VS2005 solotion.
In my assambly.cs files the AssemblyVersion was set to "1.0.*" (default in
VS2005)
In VS2005 default AssemblyVersion is "1.0.0.0".
I fixed the problem with the breaking setup project by changing the
AssemblyVersion to 1.0.0.0
in the Assembly.cs files of all my projects.
/K
"Mihir Solanki" <mi**********@hotmail.com> skrev i meddelandet
news:19*************************@msnews.microsoft. com...
Hi,
Seems you removed one or more projects after adding it to the deployment
and setting its dependencies. If you remove project and re add it then it
gives this kind of errors. you have to recreate your deployment package
or have to update dependencies.
Mihir Solanki
http://www.mihirsolanki.com
Im trying to deploy a windows service and a windows application
together with my web application in the same setup msi. It works
sometimes, but suddenly I cant build the msi. I get errors like:
"Error 2 Unable to update the dependencies of the project. The
dependencies for the object 'Processes.DLL' cannot be determined.
C:\jobb\swm\SwiftMiddlwarePolling\Package\Package. vdproj Package"
and
"Error 3 Unable to find source file
'C:\jobb\swm\SwiftMiddlwarePolling\Package\Polling Settings.DLL' for
assembly 'PollingSettings.DLL', located in
'[NEWPROPERTY1]\OMX\SwiftMiddleware'
C:\jobb\swm\SwiftMiddlwarePolling\Package\Package. vdproj Package"
What is the best way to keep all your system components in one setup
file?
Regards
Kristian
