Please let me know how to get rid of these errors, and be able to build my
installer on the new development system.
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdFinishedDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdAdminLicenseDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdAdminFolderDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdAdminConfirmDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdAdminWelcomeDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdAdminSplashDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdAdminFinishedDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdFolderDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdLicenseDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdWelcomeDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdSplashDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdCustomCheck1Dlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdConfirmDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdProgressDlg.wid'
ERROR: Unable to build dialog module named 'C:\Program Files\Microsoft
Visual Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdAdminProgressDlg.wid'
(I have ensured all the files mentioned here are present. MS Dev Env
version is 7.1.3088 (Visual Studio.NET 2003)
Thanks,
Ram Shriram
Thanks for posting. We have just received a similar report from our product
support service. Currently the situation is under investigation.
I will keep you posted if there is any new findings. By the way, could you
let me know which merge modules you are using? If we remove the merge
modules from the project, does it work?
Regards,
Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
I am using the following merge modules:
comcat.msm
oleaut32.msm(Excluded)
vc_user_atl71_rtl_x86_---.msm
vc_user_crt71_rtl_x86_---.msm
vc_user_mfc71_rtl_x86_---.msm
vc_user_stl71_rtl_x86_---.msm
comctl32.msm
msvbvm60.msm
Do you know of a workaround that I can use in the meantime?
Thanks,
Rohit
"Felix Wang" <v-f...@online.microsoft.com> wrote in message
news:oCSPG1cL...@cpmsftngxa10.phx.gbl...
Thanks for your update. I am sorry but the current workaround is to create
a new setup project with the same set of files.
I will do some further research on this issue.
I have done some tests with the merge modules. I cannot reproduce the
situation. I am using the VS.Net 2003 merge modules, as long as those from
VS 6 SP 6:
http://www.microsoft.com/downloads/details.aspx?FamilyId=F9D19334-61EC-48CF-
BB4E-3AEC65EDD50B&displaylang=en
Is there anything else special with the project? Are the project outputs
included in the setup project share the same path between the 2 machines?
Hope this helps.
"Warren Barkhuizen" <war...@prodata.co.za> wrote in message
news:824c1245.04043...@posting.google.com...
The problem was due to my having incorrect path for the banner bitmap in the
other system. Warren's suggestion below helped me isolate the error.
Thanks,
RS
"Felix Wang" <v-f...@online.microsoft.com> wrote in message
news:1J6a$1oLEH...@cpmsftngxa10.phx.gbl...
Thanks for your suggestion. I believe it will be helpful to other people
with the same problem as well.
I really appreciate it ;-)
Please feel free to post here is you have any further concerns on this
issue. Warren's comment is really valuable.