|
|
You're in the
visual studio .net general
group:Setup project build crashes Visual Studio
visual studio .net general:
We have a VS .Net 2003 solution containing five projects, two Windows
Applications, two Class Libraries and a Setup Project. The Setup Project was created on our build machine using VS Enterprise Developer and stored (with the solution in VSS). We have five developers that are working on the project using VS Professional and sharing the code via VSS. Life was good until the build machine crashed and we attempted to build the Setup project on the developer machines. We have tried three different ones with the same result: each time VS disappears completely (crashes with no error messages) soon after displaying a message something like: Building file c:\...\AppInstaller.msi. We are able to create and build simple setup projects on the developer machines. However, we cannot build the "real" one even although, thanks to VSS, it appears to be identical to that on the build machine. Any clues on what might be going wrong or how to even debug this? Thank you. Kees VanTilburg
Hi Kees,
Thanks for posting. Based on my past experience, the crash may be caused by some specific files. Some files may crash the IDE since the IDE fails to handle them gracefully. Do you have .OBJ file in your setup project? You may also exclude the files one by one to isolate the problem. 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.
Felix,
Thanks, I'll give this a try. I was hoping to avoid it, as there are many files. What I don't understand is why this would work perfectly on the build machine, but crash all other machines. They all get source files from the same VSS project. Could this be a clue as to what file? Maybe an operating system file? Kees On Fri, 28 May 2004 06:27:32 GMT, v-felwa@online.microsoft.com (Felix [quoted text, click to view] Wang) wrote:
>Hi Kees, > >Thanks for posting. Based on my past experience, the crash may be caused by >some specific files. > >Some files may crash the IDE since the IDE fails to handle them gracefully. >Do you have .OBJ file in your setup project? You may also exclude the files >one by one to isolate the problem. > >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.
Hi Kees,
I have to admit that the issue is a little bit weird, as the build process works on one machine but fails for all the others. I hope the test may help to isolate the problem. 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.
Felix,
I've found the file that is causing the crash. It is a Merge Module that we're using to install the Exception Management application block. We're using separate msm files for the exceptionmanagement.dll and the exceptionmanagement.interfaces.dll. Both msm files install their respective dll's in the GAC (Primary Output in the GAC). The msm for the interfaces dll causes the build to crash. Do you know why the msm would crash the build? And why this would not occur on the build machine? Thank you.
Hello Kees,
I suspect that particular merge module has been corrupted somehow. If we build a new one for the interfaces dll, does it help? 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.
Felix,
Thanks...I should have mentioned...I tried that without success. Could it have something to do with the reference relationship between the exception block dll and the interfaces dll? Kees On Wed, 02 Jun 2004 02:59:59 GMT, v-felwa@online.microsoft.com (Felix [quoted text, click to view] Wang) wrote:
>Hello Kees, > >I suspect that particular merge module has been corrupted somehow. If we >build a new one for the interfaces dll, does it help? > >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.
Hi Kees,
I have tried to reproduce the problem. There seems to be some problem but I cannot reproduce the exact crash situation. Could you add the MSM file to a zip and post it here as an attachment? The compressed file should be around 40K. 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.
Felix,
Here's the msm for Exception.Management.Interfaces. Thank you.
Felix,
I sent the file. It ended up on a new thread. Please see similar thread name on 6/3. Kees On Thu, 03 Jun 2004 06:39:22 GMT, v-felwa@online.microsoft.com (Felix [quoted text, click to view] Wang) wrote:
>Hi Kees, > >I have tried to reproduce the problem. There seems to be some problem but I >cannot reproduce the exact crash situation. Could you add the MSM file to a >zip and post it here as an attachment? The compressed file should be around >40K. > >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.
Hello Kees,
Thanks for uploading the file. I was able to reproduce the problem on one of my Windows XP test machine. There are many different behaviors: 1. On 2 of my Windows 2003 machines, everything builds fine. 2. On one Windows 2000 machine and one Windows XP machine with both VS.Net 2002 and VS.Net 2003, the setup project builds, but the "Microsoft.ApplicationBlocks.ExceptionManagement.Interfaces.dll" file is not packaged into the MSI at all. I will do some further research on this issue and get back to you as soon as possible. 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.
Hello Kees,
I have done some intensive research and tests. It seems to me that the root cause of the crash is the name of the assembly is too long. Note that this is not only related to the assembly name, but also the file name. Once we install a Windows Installer Platform SDK tool named "Orca", the crash no longer happens. However, the assembly with long name is silently dropped by the setup project. Currently it seems that the situation only happens to an assembly that will be put into the GAC and the project is being built on non-Windows 2003 machine. I will do some further research on this issue. 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.
Felix,
Thank you. Great job finding the problem! We don't have any Windows 2003 boxes yet in our organization. Is there any work-around for Windows XP? Is there a newer version of Window's Installer that can be installed on XP? Any idea why one of our XP boxes builds without issue? (At least it did before it died!) Could it have anything to do with the VS version (Enterprise Developer vs. Professional)? Kees On Tue, 08 Jun 2004 12:16:10 GMT, v-felwa@online.microsoft.com (Felix [quoted text, click to view] Wang) wrote:
>Hello Kees, > >This looks like a bug in Windows Installer's merge module DLL. It should be >fixed witn MSI on Windows 2003. Would it be accetable if we build the setup >project on a Windows 2003 platform? > >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.
Hello Kees,
This looks like a bug in Windows Installer's merge module DLL. It should be fixed witn MSI on Windows 2003. Would it be accetable if we build the setup project on a Windows 2003 platform? 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.
Hi Kees,
I have not yet figured out a good way to workaround this problem. Let me do some further research. I will keep you updated. 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.
Hi Kees,
Would you consider it acceptable if we rename the long name file in the merge module? After we build the setup project, we can use a Windows Installer Platform SDK tool named "Orca" to open the MSI for editing. Then let's change the name of the file back. HOWTO: Use the Orca Database Editor to Edit Windows Installer Files http://support.microsoft.com/?id=255905 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.
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |