This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Error 1935 during installation – IsSaBld, MsBuild issue
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 05, 2008
02:24 AM
Error 1935 during installation – IsSaBld, MsBuild issue
Hi All,
My setup installs a .NET assembly into GAC. My project is an InstallScript-MSI and I am using InstallShield 2008 Professional and InstallShield Standalone Build 2008.
Well, if I am using IsCmdBld or InstallShield IDE to compile my installation – the installation works without errors.
But if I am using MsBuild or IsSaBld to compile, I am receiving Error 1935, HRESULT 0x80131047 during the installation.
I found the source of the error but still not a solution.
Using MsBuild or IsSaBld:
There are two similar entries in the MsiAssemblyName table for "ProcessorArchitecture".
The difference is only the fist letter case - 'P' and 'p'. I am receiving error 1935. If I delete the ‘processorArchitecture’ entry with Orca, the installation works fine.
Name Value
ProcessorArchitecture MSIL
processorArchitecture MSIL
Using InstallShield IDE or IsCmdBld:
There is only one ProcessorArchitecture entry in MsiAssemblyName table and the installation works.
Name Value
ProcessorArchitecture MSIL
Is there an error in IsSaBld /IS support for MSBuild/?
Or maybe I must add some additional options in my .isproj file.
Thanks in advance!
Regards,
stenlly
My setup installs a .NET assembly into GAC. My project is an InstallScript-MSI and I am using InstallShield 2008 Professional and InstallShield Standalone Build 2008.
Well, if I am using IsCmdBld or InstallShield IDE to compile my installation – the installation works without errors.
But if I am using MsBuild or IsSaBld to compile, I am receiving Error 1935, HRESULT 0x80131047 during the installation.
I found the source of the error but still not a solution.
Using MsBuild or IsSaBld:
There are two similar entries in the MsiAssemblyName table for "ProcessorArchitecture".
The difference is only the fist letter case - 'P' and 'p'. I am receiving error 1935. If I delete the ‘processorArchitecture’ entry with Orca, the installation works fine.
Name Value
ProcessorArchitecture MSIL
processorArchitecture MSIL
Using InstallShield IDE or IsCmdBld:
There is only one ProcessorArchitecture entry in MsiAssemblyName table and the installation works.
Name Value
ProcessorArchitecture MSIL
Is there an error in IsSaBld /IS support for MSBuild/?
Or maybe I must add some additional options in my .isproj file.
Thanks in advance!
Regards,
stenlly
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 07, 2008
02:01 AM
I must make more exact.
I am checking the MsiAssemblyName table in MSI file using Orca and not in .ISM file.
I am checking the MsiAssemblyName table in MSI file using Orca and not in .ISM file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 07, 2008
07:43 AM
Are you seeing this behavior with all GAC-destined assemblies, or just certain ones? You mention a difference in behavior between a standalone build environment and the IDE environment; did you try MSBuild on a machine with the IDE environment, or only on the SAB environment?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 10, 2008
02:32 AM
Yes, this error occurs with all GAC-destined assemblies. Or it is better to say all in this project. I tried MSBuild on my machine (with IDE environment), the result was the same.
Well, I will create a sample project and will try this issue again.
I’ll post the results later.
Well, I will create a sample project and will try this issue again.
I’ll post the results later.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 11, 2008
02:48 AM
I found the error. The error was on my side.
The project was first developed with InstallShield 11.5. There was an error with .NET 2.0 Assemblies and GAC in IS 11.5 – ProcessorArchitecture is missing in MsiAssemblyName table. The build script was modifying MSI file to fix this error.
The project was first developed with InstallShield 11.5. There was an error with .NET 2.0 Assemblies and GAC in IS 11.5 – ProcessorArchitecture is missing in MsiAssemblyName table. The build script was modifying MSI file to fix this error.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 11, 2008
10:55 AM
Good find, and glad to hear it's working now. It's always fun when fixing a clear bug causes a problem down the road. 😄
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)