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

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

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

(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

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

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

if there is a solution for this problem?
if it is necessaryi can send a solution with this problem

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.

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

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.

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

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.

Check out this HOT-FIX
http://support.microsoft.com/kb/917036/

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)