Error during building setup with WiX and Russian localization option on

Add-in Express™ Support Service
That's what is more important than anything else

Error during building setup with WiX and Russian localization option on
 
rxtxup


Guest


Hello. I'm getting this kind of exception with WiX when Russian localiz selected.


Application Domain: DefaultDomain
Assembly Codebase: file:///C:/Program Files/Add-in Express/Add-in Express .NET for Internet Explorer/Bin/Package/VS2005/AddinExpress.IEWizard.dll
Assembly Full Name: AddinExpress.IEWizard, Version=9.0.6121.0, Culture=neutral, PublicKeyToken=4416dd98f0861965
Assembly Version: 9.0.6121.0

Exception Source: AddinExpress.IEWizard
Exception Type: System.IndexOutOfRangeException
Exception Message: Index was outside the bounds of the array.
Exception Target Site: ProcessWiXSetupTemplate

---- Stack Trace ----
AddinExpress.SetupWizard.SetupWizardForm.ProcessWiXSetupTemplate(targetFramework As String, adxInstallDir As String, primaryOutputPath As String, patchPath As String, projectGuid As String, upgradeGuid As String, setupFile As String, dependencies As String, wixNamespace As String, brokerProjectName As String, brokerCfgFileName As String, setupText As String&, productText As String&)
AddinExpress.IEWizard.dll: N 0000 (0x0) IL
AddinExpress.SetupWizard.SetupWizardForm.CreateSetupProject(primaryOutputPath As String)
AddinExpress.IEWizard.dll: N 2589 (0xA1D) IL
AddinExpress.SetupWizard.SetupWizardForm.CreateSetupProject(project As Project, targetFramework As UInt32)
AddinExpress.IEWizard.dll: N 0069 (0x45) IL
AddinExpress.IE.Wizard.ADXIEPackage.Exec(guidCmdGroup As Guid&, cmdID As UInt32, nCmdexecopt As UInt32, pvaIn As IntPtr, pvaOut As IntPtr)
AddinExpress.IEWizard.dll: N 0715 (0x2CB) IL

[QUOTE]
I'm using VS 2012 Pro En, latest Add-in-Express, latest WiX. And my project uses .Net 2.0 addon works in debug mode.
Posted 16 Feb, 2014 04:48:04 Top
rxtxup


Guest


Also how to make msi to register all .dlls without distributing setup.exe?
Posted 16 Feb, 2014 06:52:30 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
 Joined: 2004-07-05
Hello,

Thank you for the debug report. Please create a new setup using the <default> localization and then set the Language attribute to 1049 in the Product and Package elements of the WiX project.

Also how to make msi to register all .dlls without distributing setup.exe?

Just remove the InstallPrivileges attribute from the Package element. In this case the UAC popup will appear whenever the setup needs to execute a task with elevated privileges.
Posted 17 Feb, 2014 08:33:34 Top
rxtxup


Guest


Sergey Grischenko writes:
Also how to make msi to register all .dlls without distributing setup.exe?

Just remove the InstallPrivileges attribute from the Package element. In this case the UAC popup will appear whenever the setup needs to execute a task with elevated privileges.

I tried to remove this line, still addon not registered after .msi finished copying files.
Posted 17 Feb, 2014 09:57:43 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
 Joined: 2004-07-05
Do you get the UAC popup during the installation process? What is the installation folder of your add-on?
Please note, adxregistrator creates a log in the '.\Documents\Add-in Express' directory. You can send it to me on the support e-mail. I will check it.
Posted 17 Feb, 2014 11:03:55 Top
rxtxup


Guest


Hi Sergey Grischenko, sent it to support@add-in-express.com
Posted 17 Feb, 2014 11:39:15 Top
rxtxup


Guest


Hi Sergey Grischenko, as you can see even with UAC prompt Exception raised.
Posted 17 Feb, 2014 11:50:05 Top
Andrei Smolin


Add-in Express team


Posts: 18830
 Joined: 2006-05-11
Hello Eugene,

Thank you for sending us the log. The log shows that you install the add-on using a standard user's permissions. That is, the elevation dialog that Sergey asked about occurs too late. You need to start the installer by running setup.exe, not .MSI. Note that if this does NOT produce the elevation dialog immediately, you need to run setup.exe by right-clicking it and choosing "Run as administrator" in the context menu. Actually, I would recommend that you check the corresponding section under the section Deployment Step-by-steps in the PDF file in the folder {Add-in Express}\Docs on your development PC. These sections are written in the "language" of standard setup project in VS 2005-2010; you need to "translate" the section to the "language" of WiX.

Hope this helps.


Andrei Smolin
Add-in Express Team Leader
Posted 18 Feb, 2014 00:29:59 Top
Andrei Smolin


Add-in Express team


Posts: 18830
 Joined: 2006-05-11
In case you generate a single .MSI instead of .MSI+setup.exe, to run your .MSI with elevated permission, you can start the command prompt with elevated permission and then execute MSIEXEC.EXE with corresponding parameters to start your .MSI.


Andrei Smolin
Add-in Express Team Leader
Posted 18 Feb, 2014 00:35:48 Top