Search

Setup project error: Unable to update the dependencies of the project by Lee Gillie

Closed
as Not Reproducible Help for as Not Reproducible

71
2
Sign in
 to vote
Type: Bug
ID: 119625
Opened: 3/23/2006 1:02:08 PM
Access Restriction: Public
Duplicates: 107429
10
Workaround(s)
48
User(s) can reproduce this bug
Hierarchy section of a setup project becomes corrupt. Once this happens "Unable to update the dependencies of the project" errors occur when building setup. Also REFRESH DEPENDENCIES fails with "The operation can not be completed".
Details (expand)
Product Language
English
Version
Visual Studio 2005 Release Candidate
Category
Other
Operating System
Windows 2000 Professional
Operating System Language
US English
Steps to Reproduce
Create component projects in VS 2003. Create an appliction project in VS 2003. Convert solution containing all projects to VS 2005. Add setup project under VS 2005. Build setup. Exit. Return to solution. Advance version of setup project, each component, and the application. Build setup. Reported errors are then seen.
Actual Results
Examining Setup.vdproj file reveals the Hierarchy section contains bogus and duplicate entries.
Expected Results
Project to build without error. Suggested we delete Hiearchy section that VS will remake it, but this has never worked for us, and does not correct the problem. We have had limited success with a tool we wrote to walk dependencies of application using reflection, and remaking the Hierarchy section ourselves, but our knowledge of what is here is too incomplete to work in all scenarios. If we don't advance versions then installer won't update components. Costs us many hours each week. Many others have communicated similar symptoms to me.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Dorothy Robitaille on 4/6/2012 at 11:11 AM
I have converted one of my VB.net 2005 applicaiton into VB.net 2010. I have VB.net 2010 Premiun version. When I open the applicaiton using VB.NET 2010 and I got this error. Unable to update the dependencies of the project. The description says :An error occurred while validating HRESULT = ''80004005: I try to rebuild Solution and it will not allow to do so. Any ideas? Thank you very much!!
Posted by A_Unique_Name on 2/14/2011 at 1:06 PM
I have a solution with one C# project and an MSM. These were all created with VS2010; not converted from earlier version. The exact problem I am seeing is this:

Load solution into VS2010 IDE.
Invoke REBUILD ALL.
The C# project builds fine.
The MSM will not build. I get this: "ERROR: Unable to update the dependencies of the project."
Without exiting VS2010 IDE, invoke REBUILD ALL again. This time it builds everything ok.

I think our workaround will be to use InstallShield.
Posted by James Peckham on 2/13/2011 at 12:17 PM
I just got this issue when building using exec task in nant and devenv.com. it builds beautifully in the vs2010 gui, but it dies with nant. THis particular setup project references a few dlls directly that have other dll references. Even if i exclude all of those detected dependencies it still fails to 'update dependencies'

My workaround was to just move the setup project into 1 solution with all of the class library projects that would make my other dlls. this issue was particular to voyager / corillian online licensed (a fiserv product). Perhaps you can work with them on it.

basically i had FiName.Authentication.Operations.dll, FiName.Banking.Operations.dll, FiName.Utilities.dll, and FiName.Host.dll all added and it was breaking on the log4net dependency during the NAnt build. I am using nant 0.86.

This was working 100% fine in visual studio 2008 but broke in visual studio 2010.
Posted by skimming88 on 9/30/2010 at 7:18 AM
This fix seems to work for me. I'm adding the link here (it is also seen in the Workarounds tab) so that others can find it more easily.

https://connect.microsoft.com/VisualStudio/feedback/details/552799
Posted by Jerry Chia-Ming Liang on 9/28/2010 at 8:22 PM
Help! My setup was working perfectly in vs2008 however, when I upgraded it to vs2010, I get this error and I couldn't create the setup file for my project. Does anyone know how to solve this problem?? I wonder why this bug is closed as well..
Posted by RSudama on 7/22/2010 at 8:22 AM
Hello, this is many years and multiple releases later (VS 2010) - there's no way this is closed!!! The web setup projects are almost completely unusable because of this issue with calculating the dependencies. I have tried all of the workarounds regarding editing of the project file, and while they might solve an immediate problem temporarily, the installer project is "smart" enough to put all of the problems right back when you try to do anything at all.

If you can't fix this problem properly, please, please just provide an option to turn off the dependency checking. This would be a really nice feature if it worked properly, but it doesn't. I'd at least like to have the option to resolve the dependencies for myself if you can't do it right.
Posted by ghoshy on 7/11/2008 at 4:44 AM
Is this issue resolved. I could see the status as closed. If that is the case where is the solution or hotfix? Is that the workaround the only solution available. Please comment
Posted by Microsoft on 5/8/2007 at 5:53 PM
Thanks for reporting this issue. We are not able to reproduce this issue without hand-modifying the Hierarchy section of project file.

Could you please attach a solution file along with complete steps that would get setup project into this state.

If anyone else is also facing the same issue & can reproduce this problem using Visual Studio, please send us the solution file with complete steps.

Thanks,
Visual Studio Application deployment team.
Posted by 8638C1F1-1A59-4220-9F2F-020A96E57FE0 on 1/26/2007 at 6:18 AM
if there is a solution for this problem?
if it is necessaryi can send a solution with this problem
Posted by Brecht Yperman on 9/7/2006 at 11:26 PM
Noticed something very strange when manually editing the setup .vdproj file (with WordPad).

All of a sudden in the file (in Hierarchy), an Asian character appears and the formatting of the text changes...

I've put a screenshot on http://www.invenso.com/119625.png
Posted by Enrique Blanco on 8/6/2006 at 11:30 AM
Is this solved already? Anybody at MS on it now?
I can provide a failing solution...
I think the problems started when I added the solution to VSS, but I can't assure. Fell free to contact me for more info.

Enrique Blanco
MCSD MCDBA
enrique.blanco@gmail.com
www.eblanco.com
Posted by Microsoft on 7/20/2006 at 2:47 PM
(My apologies: I tried to post this request to this site months ago, but it never appeared.)

Would anyone be willing to contact me directly with their solution? I can understand why no one would want to post a repro onto newsgroup forums or on the MS feedback site. I will will make every reasonable effort to make sure that you feel comfortable in supplying a repro. Please contact me at vsw586416@hotmail.com if you are interested.

Thanks,
Mike Wade
Visual Basic .NET
Posted by Microsoft on 4/27/2006 at 4:46 PM
Thanks for reporting this issue, Lee. I am not able to reproduce this issue without hand-modifying the Hierarchy section of the project file. Could you (or anyone else) please attach a solution along with complete steps that will get the setup project into this state?

Thanks,
Mike Wade
Visual Basic .NET
Posted by Microsoft on 3/29/2006 at 10:22 PM
Thank you for reporting this issue. The team will take a look and post some more comments once they have more information.

- David Guyer -- Visual Basic
Sign in to post a workaround.
Posted by Lee Gillie on 5/19/2006 at 2:31 PM
I have consistently used this method to get around this bug instead of rebuilding my setup projects. This applies to both merge module projects AND setup projects. Manually remove the data in the Hierarchy and Files section of the project files.

1. Open .VDPROJ file
2. Find the "Hierarchy" section. Delete everything so the section looks like this:

    "Hierarchy"
    {
        
    }

3. Find the "File" section. Delete everything so the section looks like this:

        "File"
        {
            
        }

4. Reload the project
5. Rebuild the project.
Posted by DaveSimmonds on 7/13/2006 at 3:11 PM
I have successfully worked around this issue with the following steps:
1. Remove the offending setup project from the solution
2. Rebuild the solution
3. Re-add the setup project to the solution
4. Rebuild the solution
Posted by NeuroSpeech on 8/22/2006 at 3:53 PM
No wonder, when pirated software is available why we should pay because even after paying for software, when it doesnt work, we are asked for $250/hr support from microsoft professional? 10000s of time we get this error and it is so annoyning rebuilding whole setup again and again and again and we cant even modify deployment project because once it is modified, it has some chinese characters and if those gets moved or deleted, the VS says the setup project is corrupt.
Posted by Lee Gillie on 9/18/2006 at 7:28 AM
Check out this HOT-FIX
http://support.microsoft.com/kb/917036/
Posted by Tegel on 2/1/2007 at 4:13 AM
1. From the setup project, remove the "Primary output from YourProject(Active)"
2. Remove the setup project itself.
3. Edit setup project file(.vdproj) and see if there still are any traces left. For me the two offending assemblies were still included under the "File"-section!!? I removed all these lines. Example of removed lines for one assembly:
            "{9F6F8455-1EF1-4B85-886A-4223BCC8E7F7}:_1B16D3C4EC5C1F94D9D09AB4DFE14163"
            {
            "AssemblyRegister" = "3:1"
            "AssemblyIsInGAC" = "11:FALSE"
            "AssemblyAsmDisplayName" = "8:MyCompany.Project.Myassembly, Version=1.0.0.0, Culture=neutral, processorArchitecture=MSIL"
                "ScatterAssemblies"
                {
                    "_1B16D3C4EC5C1F94D9D09AB4DFE14163"
                    {
                    "Name" = "8:MyCompany.Project.Myassembly.dll"
                    "Attributes" = "3:512"
                    }
                }
            "SourcePath" = "8:MyCompany.Project.Myassembly.dll"
            "TargetName" = "8:"
            "Tag" = "8:"
            "Folder" = "8:_59AA84A41D8843648F2D635854FBF177"
            "Condition" = "8:"
            "Transitive" = "11:FALSE"
            "Vital" = "11:TRUE"
            "ReadOnly" = "11:FALSE"
            "Hidden" = "11:FALSE"
            "System" = "11:FALSE"
            "Permanent" = "11:FALSE"
            "SharedLegacy" = "11:FALSE"
            "PackageAs" = "3:1"
            "Register" = "3:1"
            "Exclude" = "11:FALSE"
            "IsDependency" = "11:TRUE"
            "IsolateTo" = "8:"
            }
4. Save and add the setup project to your solution again
5. Add Primary output and... "Fina fisken!"(Swedish humor)
Posted by Jeff Hunsaker on 8/26/2010 at 10:58 AM
See Hans' and my response here:
http://social.msdn.microsoft.com/Forums/en-US/csharpide/thread/83e136a2-a93f-4abb-8bf9-ba6eafba5a2c/#8e42648b-00e4-4fd8-9ed4-0b6519871c2e

Providing a full path to referenced assemblies resolved this issue for me.
Posted by bralston on 8/31/2010 at 1:18 PM
For VS2010, there is now a hotfix available. See this Connect thread: https://connect.microsoft.com/VisualStudio/feedback/details/552799
Posted by TimPartridge on 9/28/2011 at 1:25 PM
This Hotfix worked for Visual Studio 2010 for me.

https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=30681
Posted by TimPartridge on 1/11/2012 at 7:09 AM
Update: The error reappeared after disappearing for me using this hotfix:

https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=30681

I reapplied the hotfix and it went away again.

Tim
Posted by RDIWill on 2/2/2012 at 2:08 PM
In my case the deployment project installs a windows service and that service uses 1og4net (not sure if it is related but saw an earlier post so figured I would mention it). The service was installed and -running- on the same machine I was trying to build the deployment project on. In looking at the Outputs array in the properties of the Primary output from <deployment project name> it showed: The application called an interface that was marshalled for a different thread. (Exception from HRESULT: 0x8001010E (RPC_E_WRONG_THREAD)). This lead me to believe some other application was running and had a lock on something need for the build. As soon as I turned of my service I could build.
© 2012 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement