Unable to update the dependencies of the project
I have had this error every time I try to check my program into source control after making changes. The project builds and works fine until I check it in and check it back out then it won’t build. I have deleted the setup project and built a new one only to have the same problem after checking it into source control. It also givs me a warning that " Assembly ' FolderName\FileName.exe ' is incorrectly specified as a file. Any suggestions would be helpful.
I need a little more information to try to narrow things down. I should mention that there do seem to have been similiar problems reported before [see:
http://www.dotnet247.com/247reference/msgs/49/247883.aspx]. That posting also mentions setup builds breaking after doing a checkout from SCC (although they used VSS) in their case.
A few questions:
1) Is there more to the error message that just "Unable to update the dependencies of the project"? Most of the posts I've seen with this error also include the path to the dependency in the error message.
2) What kind of project(s) are we dealing with? Is the setup project referencing web projects, C# projects, etc. ?
3) Have you tried doing a Save All Files and then doing Compare on the setup project's files after you've done the CheckIn and CheckOut to see what has changed? There is a posting about setup project builds breaking due to AssemblyVersion changing [see: http://www.thescripts.com/forum/thread420289.html].
Thanks,
Ben
Ben -
Although it is marked as the answer, I am not sure this answers the question.
What I find is that if I have several projects in a solution, and start
advancing version numbers on multiple projects before doing a build of
the setup project, it will corrupt the setup project. At this point I
must trash the setup project and start over. I do not use VSS
integrally with VS IDE, and this can happen without involving any check
in or check out.
It is my theory the GUIDS on the dependency chain for complex solutions
with perhaps multiple projects dependent upon other projects do not
update properly when version numbers are advanced. It is as though
these projects become "orphaned" in the application folder of the setup
project. You can remove the original output project, and yet these
dependency projects remain, still with the error.
Please let us know a fix is in the pipe. Rapid development stops when I
get my last changes made, do my version # advances, so setup will
update each component, then only to have the setup kit become corrupt
and throw the work hours behind.
I am experiencing the same issue. Whenever I check out my web setup project to advance the version number it fails to compile with the message:
Unable to update the dependencies for this project
After which I need to remove the setup project from my solution and start another one from scratch.
Obviously this is tedious and time consuming, any suggestions?
Bob
Me too - I just got this problem with a project I have been working on for a couple of months. Having found this thread, I removed the setup project and was just about to start another one from scratch, when I tried reloading it (File, Add, Existing Project) - and Hey! everythings back to normal. Dependencies all listed in the explorer window, no error messages, all ok. So just in case you've not tried that . . .
pg
I'd like to also confirm this is a serious problem. I have built, destroyed and rebuilt the setup project several times. This problem usually occurs that the worst possible time, like hours before a release or a big demo. I spent almost a week with the Microsoft people. I was able to demonstrate the problem, but because I couldn't package it up and send it to them, they were useless.
The problem appears exactly as described. You get your project working just right, you package it up and then check everything in because your QC people tell you that it is ready to go out to testers or marketing. Then, you begin to change things, because that's what you do as an engineer, you change build numbers, add modules, etc. Then when you go to check out the deployment project because you've got another release coming up, you get the infurating message: "Unable to update the dependancies of the project."
One work-around that I use under duress is to go into the .vdproj file with notepad and delete every section mentioned in the error messages. The project seems to build after that.
I can confirm this as yet another extremely annoying bug. If a
new release warrants a version number change in any of the modules then
the setup project is broken.
ERROR: Unable to update the dependencies of the project. The dependencies for the object 'xxxx.dll' cannot be determined.
The problem occurs with ever DLL included in the solution. If I
right-click -> Refresh Dependencies on the Detect Dependencies
folder in the solution explorer then I get a simple message box "The
operation could not be completed" from Microsoft Visual Studio.
Would be really nice if I could find out WHY the operation could not be completed. Even a small clue would be nice.
btw: Crashed the document explorer twice more trying to find info about this :-(.
This continues to be a huge problem. For example, one solution contains
18 projects. All have explicit version numbers. Some are converted VB
from VS 2003, some created in VS 2005, and one CS. I can get a clean
build, exit Visual Studio, get a clean build, and then go to advance
the manual versions first on the setup project, then on assemblyinfo.vb
on a changed component, and all components that call it, right on up
the tree to the primary output project. Do the build now, and I get
Rebuild All started: Project: PPSManager, Configuration: Debug Any CPU
C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Vbc.exe/noconfig /baseaddress:11000000
/imports:Microsoft.VisualBasic,System,System.Collections,System.Data,System.Diagnostics,System.Drawing,System.Windows.Forms
/nowarn:42016,42017,42018,42019,42032 /optioncompare:Binary
/optionexplicit+ /optionstrict+ /removeintchecks-
/rootnamespace:PPSManager /doc:obj\Debug\PPSManager.xml
/define:"CONFIG=\"Debug\",DEBUG=-1,TRACE=-1,_MyType=\"WindowsForms\",PLATFORM=\"AnyCPU\""
/reference:"C:\Program Files\Microsoft.NET\Primary Interop
Assemblies\adodb.dll","D:\ODPNET20\Core\Genuine
Channels\2.5.X\DLL\Framework
2.0\Release\GenuineChannels.dll","D:\ODPNET20\PPS\PPS
System\SpeedPrint\IRCSpeedPrint\bin\IRCSpeedPrint.dll",D:\ODPNET20\Core\ODPBatchControl\ODPBatchControl\bin\ODPBatchControl.dll,D:\ODPNET20\Core\ODPDisplayNET\bin\ODPDisplayNET.dll,"D:\ODPNET20\PPS\PPS
System\ODPInsert\bin\ODPInsert.dll",D:\ODPNET20\Core\ODPMessage\bin\ODPMessage.dll,"D:\ODPNET20\PPS\PPS
System\PPSConfigNET\bin\PPSConfigNET.dll","D:\ODPNET20\PPS\PPS
System\PPSInserterDef\bin\PPSInserterDef.dll","D:\ODPNET20\PPS\PPS
System\PPSPageNET\bin\PPSPageNET.dll","D:\ODPNET20\PPS\PPS
System\PPSProgressMessages\bin\PPSProgressMessages.dll","D:\ODPNET20\PPS\PPS
System\PPSServiceLib\bin\PPSServiceLib.dll","D:\ODPNET20\PPS\PPS
System\PPSTables\bin\PPSTables.dll",C:\WINNT\Microsoft.NET\Framework\v2.0.50727\System.Data.dll,C:\WINNT\Microsoft.NET\Framework\v2.0.50727\System.dll,C:\WINNT\Microsoft.NET\Framework\v2.0.50727\System.Drawing.dll,C:\WINNT\Microsoft.NET\Framework\v2.0.50727\System.ServiceProcess.dll,C:\WINNT\Microsoft.NET\Framework\v2.0.50727\System.Windows.Forms.dll,C:\WINNT\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll
/main:PPSManager.My.MyApplication /debug+ /debug:full /optimize-
/out:obj\Debug\PPSManager.exe
/resource:obj\Debug\PPSManager.DGButtonColumn.resources
/resource:obj\Debug\PPSManager.FormattableTextBoxColumn.resources
/resource:obj\Debug\PPSManager.frmAbout.resources
/resource:obj\Debug\PPSManager.frmConfirmationAddressLookup.resources
/resource:obj\Debug\PPSManager.frmConfirmationEditor.resources
/resource:obj\Debug\PPSManager.frmLogViewer.resources
/resource:obj\Debug\PPSManager.frmMain.resources
/resource:obj\Debug\PPSManager.frmReadyToRun.resources
/resource:obj\Debug\PPSManager.frmSubmit.resources
/resource:obj\Debug\PPSManager.frmVolumeNavigator.resources
/resource:obj\Debug\PPSManager.frmWeights.resources
/resource:obj\Debug\PPSManager.Resources.resources
/resource:obj\Debug\PPSManager.PPSManagerDataGrid.resources
/resource:obj\Debug\PPSManager.Volume.cur /target:winexe /warnaserror-
/win32icon:PPSManager.ico AssemblyInfo.vb Database.vb
DataGridFormatCellEventArgs.vb DataGridImageColumn.vb DGButtonColumn.vb
DiagnosticMessage.vb FormattableTextBoxColumn.vb frmAbout.vb
frmConfirmationAddressLookup.vb frmConfirmationEditor.vb
frmLogViewer.vb frmMain.vb frmReadyToRun.vb frmSubmit.vb
frmVolumeNavigator.vb frmWeights.vb Globals.vb MenuItemWithData.vb "My
Project\Application.Designer.vb" "My Project\Resources.Designer.vb"
PPSManagerDataGrid.vb RemoteServiceMonitor.vb SpeedPrintController.vb
WatchExecutionProgress.vb
PPSManager -> D:\ODPNET20\PPS\PPS System\PPSManager\bin\PPSManager.exe
Rebuild All started: Project: Setup, Configuration: Debug
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ODPRegistry.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'PPSServiceLib.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'IRCSpeedPrint.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ODPDisplayNET.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ODPInsert.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ODPMessage.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ODPBatchControl.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ODPFtpNET.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'PPSConfigNET.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'GenuineChannels.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ICSharpCode.SharpZipLib.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'PPSInserterDef.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ODPMailslotNET.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'PPSProgressMessages.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'PPSTables.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ODPZipNET.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'PPSPageNET.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'Interop_MSDASC.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'Interop.Signed.DAO.dll' cannot be determined.
========== Rebuild All: 17 succeeded, 1 failed, 0 skipped ==========
The ONLY way I know to reliably deal with this is dropping and
re-adding the primary output, and then going back and making all of the
settings for components is very time intensive and error prone.
Sometimes I have to delete the setup project and start over. I can tell
my boss my work is done, and instantly add another 1 to 2 hours before
I can deliver a working setup kit.
Some have found little tricks and tweaks, but none have worked for me.
I don't really understand what is happening, but I know it has a lot to
do with advancing version numbers. If I don't advance version numbers
then MSI won't install the updated components!
If this has bitten anyone else, I think you need to add to this thread
so they can see this is not isolated. I am pretty sure others are
having the same issue. I think we were WAY TO PREMATURE marking this
thread as being ANSWERED!!!
You said ...
"I think we were WAY TO PREMATURE marking thisthread as being ANSWERED!!!"
ABSOLUTELY. !!!Can
you repost as a new question. I'll have a couple of hours spare later
this week and can spend some time trying to make a repo and will post
too.
This is a MAJOR annoyance. btw: Are you using
SourceSafe? I have not had this problem occur on solutions that aren't
under source control.
After the setup project screws up the
dependencies right-click -> Refresh Dependencies on the Detected
Dependencies folder in the project produces an unreported background
exception and a little message box saying Error....
My solution is the same as yours. Recreate the setup project. (not trivial in my case either).
DeadlyTrev.
I have reposted in a couple of flavors.
Using VSS, but not integrated with the IDE.
I found solutions which contain projects converted from VS2003 may be
suspect. For me, advancing versions manually (before kitting) seems to
be suspect.
I theorized the "Hierarchy" section of the Setup.vbproj file is the
only corrupt part. I studied it a bit, and wrote some quick ugly code
to regenerate it by using reflection to walk the assembly dependencies,
and managed to resurrect several big corrupt setup projects.
Now rather than starting a new SETUP project from scratch, and
forgetting some settings, and all the time, I can be back up and going
in a minute or so. It is still a big pain, though.
With VSS unbound from the IDE I find the problem less likely but still occurs. I've also been able to recover by hacking about with the Hierarchy section in the vdproj file (confirming your findings that this is the part that screws up when things go awry) but have also made things worse on occasion.
I have a 32 step written script (on paper!!) to follow when rebuilding my deployment project. Tedious, time consuming cutting and pasting of GUIDs and strings and browsing for the same files over and over again. It's the bloody dark ages!!
DSS. Vic. Oz
This will be difficult to solve in the forums, but I'll fire a few arrows in the dark and hope one of them hits.
1) Any chance there was a database project in your solution? We've seen this error a couple of times when there is a database project in the solution.
2) I believe the Hierarchy section is only supposed to provide hints about dependencies and their owners. If you think this is the area giving you problems, I think you can safely delete it, and it will be re-generated automatically.
3) Finally, I see you mentioned that this happens when your solution contains projects converted from VS 2003. Are these projects still under development, or could you contine to use the VS 2003 version? Did you try packaging these with a setup project in VS 2003? If so, did you get similar failures?
4) Have you raised this issue through ProductFeedback or PSS? You can log a product feedback bug at: http://lab.msdn.microsoft.com/productfeedback/default.aspx
1) No database in the solution
2) I tried it. The project loads fine, but when I build the setup
project, which was otherwise working I get the following. Also, I
looked at the setup file, and the Hierarchy section was not there. To
confirm I deleted the line that says "Hierarchy", the "{" which
immediately follows it, and all the lines to the next "}" at the same
level. Have you actually tried this?
Build started: Project: Setup, Configuration: Release
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ODPZipNET.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'Interop.Signed.DAO.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'Interop_MSDASC.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'PPSPageNET.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ODPInsert.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ODPFtpNET.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ODPMessage.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'PPSProgressMessages.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'PPSServiceLib.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'ICSharpCode.SharpZipLib.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'GenuineChannels.dll' cannot be determined.
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'PPSConfigNET.dll' cannot be determined.
========== Build: 9 succeeded or up-to-date, 1 failed, 0 skipped ==========
3) Converted projects are now using new features of Framework 2.0
4) I will post the bug
Hmmm, well I could have sworn I tried deleting the hierarchy ages ago, and it automatically getting restored. But no doubt, when I delete it now, things become busted just as you describe.
I'm sorry, I can't hink of any nice work-arounds offhand. I will continue to look into this issue.
1. Yes, there is a database project in the solution.
2. If I delete the hierarchy section in the project file I just get the same series of "
ERROR: Unableto update the dependencies of the project. The dependencies for
the object 'xxxx' cannot be determined."
messages.
3. This solution and all component projects were created from scratch in VS2005.
