Ville
-
Posts
3 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Ville
-
-
Great! Thanks!
-
I'm getting the following error after pressing Start in All-In-One Integrator.
However v 1.4.1.11 works ok.
Exception:
***********************************
Form: frmAllInOne (False)
Status:
Anti-Virus: True
Version: 1.4.1.12
Unhandled Exception: InvalidArgument=Value of '0' is not valid for 'startIndex'.
Parameter name: startIndex
StackTrace: at System.Windows.Forms.ListView.FindItemWithText(String text, Boolean includeSubItemsInSearch, Int32 startIndex, Boolean isPrefixSearch)
at System.Windows.Forms.ListView.FindItemWithText(String text, Boolean includeSubItemsInSearch, Int32 startIndex)
at (Object , String , Boolean , Int32 )
at A..(Object , String , Boolean , Int32 )
at A..(Object , EventArgs )
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
InnerException:
Source: System.Windows.Forms
TargetSite: System.Windows.Forms.ListViewItem FindItemWithText(System.String, Boolean, Int32, Boolean)
Data: System.Collections.ListDictionaryInternal
Form History: frmStartup, frmToolsManager, frmAntiVirus, frmWIMManager, frmAllInOne,
Open Forms: frmStartup, frmAllInOne,
"Name already in use" bug?
in Win Toolkit
Posted
Hi
I'm trying to add a silent installer setup.exe but I get an error of "name already in use", even though my other 30 silent installers are not named setup.exe. I was able to get around this by modifying .ini file directly.
Could there be a bug in the naming check process?
Anyway, I love the WinToolkit