Search

"Refresh Dependencies" fails in Setup Project by hurleyp

Closed
as Not Reproducible Help for as Not Reproducible

3
0
Sign in
to vote
Type: Bug
ID: 106195
Opened: 6/29/2005 5:50:40 PM
Access Restriction: Public
1
Workaround(s)
5
User(s) can reproduce this bug
I have a legacy VC++/MFC solution that includes a setup/deployment project. Right-clicking "Detected Dependencies" to run the "Refresh Dependencies" command generates the following error message: "The operation could not be completed. Exception occurred."
Details (expand)
Product Language
English
Version
Visual Studio 2005 Beta 2
Category
Deployment
Operating System
Windows XP Professional
Operating System Language
English
Steps to Reproduce
Run the "Refresh Dependencies" command on an existing project. Note that this project is an upgrade from the previous (ie current release) version of Visual Studio.
Actual Results
Error message "The operation could not be completed. Exception occurred." No further details or information on the nature of the exception is provided by the IDE.
Expected Results
A refreshed list of setup project dependencies.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 7/26/2005 at 6:25 PM
Hi,

Thanks for submitting this bug report. To help us debug and understand this issue, can you attach a Visual Studio 2003 Setup project for which this issue was occuring?

Thanks,
-Patrick Darragh
VB PM
Posted by Microsoft on 7/10/2005 at 4:37 PM
Thank you for submitting this issue. I'm passing it to the feature team to take a look.

-Shamez
Posted by hurleyp on 6/30/2005 at 4:04 PM
Additional info: "Refresh dependencies" operation works on new "Setup" project added to existing legacy project. Work around is to replace existing legacy setup project with new setup project.
Sign in to post a workaround.
Posted by TimPartridge on 12/6/2011 at 7:52 AM
This seems like a duplicate of https://connect.microsoft.com/VisualStudio/feedback/details/119625/setup-project-error-unable-to-update-the-dependencies-of-the-project#

This Hotfix worked for Visual Studio 2010 for me.

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