Unable to build dialog module (Setup project)
Gregory Hassett
the "primary output of <my project>", the dependencies that setup discovered
(mfc70ud.dll and msvcr70d.dll), and two merge-modules that I added
(isapi_files.msm and soap_core.msm). However, when I build the project, I
get the following errors. Note that the .wid and .wim files that the
compiler is complaining about DO in fact exist in the directories it
names -- what's going on?
-- Thanks, Gregory Hassett
ERROR: Unable to build dialog module named 'd:\Program Files\Microsoft
Visual Studio
.NET\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdAdminFolderDlg.wid'
ERROR: Unable to build dialog module named 'd:\Program Files\Microsoft
Visual Studio
.NET\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdAdminWelcomeDlg.wid'
ERROR: Unable to build dialog module named 'd:\Program Files\Microsoft
Visual Studio
.NET\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdAdminConfirmDlg.wid'
ERROR: Unable to build dialog module named 'd:\Program Files\Microsoft
Visual Studio
.NET\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdProgressDlg.wid'
ERROR: Unable to build dialog module named 'd:\Program Files\Microsoft
Visual Studio
.NET\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdAdminProgressDlg.wid'
ERROR: Unable to build dialog module named 'd:\Program Files\Microsoft
Visual Studio
.NET\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdWelcomeDlg.wid'
ERROR: Unable to build dialog module named 'd:\Program Files\Microsoft
Visual Studio
.NET\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdFolderDlg.wid'
ERROR: Unable to build dialog module named 'd:\Program Files\Microsoft
Visual Studio
.NET\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdConfirmDlg.wid'
ERROR: Unable to build dialog module named 'd:\Program Files\Microsoft
Visual Studio
.NET\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdFinishedDlg.wid'
ERROR: Unable to build dialog module named 'd:\Program Files\Microsoft
Visual Studio
.NET\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdAdminFinishedDlg.wid'
ERROR: Unable to build user interface module located at 'd:\Program
Files\Microsoft Visual Studio
.NET\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdBasicDialogs.wim'
Gregory Hassett
double-click on the error message.
General failure building deployment project
See Also
Getting Help from Microsoft Product Support Services
There has been an internal failure while attempting to build a deployment
project.
To correct this error
Make note of the exact text in the error message.
Contact Microsoft Product Support Services and report the error.
David Guyer [MS]
them that is interfering with the dialog files. This shouldn't be it, since
MSM's aren't supposed to include any UI, but it's worth a try.
I would also try to Repair the Visual Studio .NET install.
An advanced thing to check would be to use ORCA to open the .WID files and
make sure that the Language property in the ModuleSignature table is 1033.
I hope that helps, if not we'll keep trying. I haven't seen a failure of so
many dialogs at once, and I've never seen this failure with the release
version.
--
-------
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
"Gregory Hassett" <ghas...@nospam.com> wrote in message
news:uoR4gtvuBHA.2592@tkmsftngp07...
Gregory Hassett
VS.NET (actually taking the opportunity to upgrade to the Enterprise edition
that came with my most recent MSDN susbscription package). Problem still
exists when the MSM files are present. I got the MSM files directly from
Microsoft's site (forget the exact URL but it was clearly marked "the MSM
files you need for redistribution"). Should I be including some other MSM
file in addition to ISAPI_FILES.MSM and SOAP_CORE.MSM? Could I have
corrupt MSM and/or WID files (even after a re-installation)?
// thanks! // greg //
"Gregory Hassett" <ghas...@nospam.com> wrote in message
news:uoR4gtvuBHA.2592@tkmsftngp07...
Gregory Hassett
Toolkit 2.0 SP2 Redistributable Files" link.
http://msdn.microsoft.com/code/default.asp?url=/code/sample.asp?url=/msdn-fi
les/027/001/580/msdncompositedoc.xml
// thanks // greg //
"Gregory Hassett" <ghas...@nospam.com> wrote in message
news:uoR4gtvuBHA.2592@tkmsftngp07...
Ted Howard
We have 1 solution that builds an install using the output from other
solutions (dll's & 1 exe).
msxml3.msm
Revision: {587049C9-7513-4CC3-99EA-8661ACD8A6E8}
1. Build returned similar errors.
2. Removed msxml3.msm, msvcp60.msm, msvcrt.msm.
3. Build works.
4. Added msvcp60.msm & msvcrt.msm.
5. Build works.
6. Added msxml3.msm
7. Build fails with new error messages:
WARNING: Error merging 'msxml3.msm': Unable to merge data from the merge
module because it conflicts with existing data in the package.
MergeModule: table='Directory' row='TARGETDIR'
Database: table='Directory' row='TARGETDIR'
ERROR: Unable to import merge module 'msxml3'
"Gregory Hassett" <ghas...@nospam.com> wrote in message
news:uoR4gtvuBHA.2592@tkmsftngp07...
David Guyer [MS]
our Dialogs look incorrect, since we load them last, but the error message
is misleading.
We are working to try to resolve the issue and determine the best approach
as well as the root cause.
--
-------
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
"Ted Howard" <n...@one.com> wrote in message
news:uYBicg6wBHA.2052@tkmsftngp07...
Ted Howard
Microsoft merge modules have errors in them?! I mean, I know that Msi's &
Msm's are incredibly complex, but it seems like Microsoft should be able to
get it right? Maybe you should outsource that work to InstallShield like you
seem to have done with all MSI creation tools (I don't regard VS.Net's Setup
projects as valid examples).
-Ted
"David Guyer [MS]" <dav...@online.microsoft.com> wrote in message
news:#$dOMH7wBHA.2104@tkmsftngp02...