PDA

View Full Version : Explosion in the wizard 2.0



A Marchini
06-03-2007, 12:40 AM
I opened up 2.0 and found this.
Start the wizard, select vixen standard sequence
Next , Next
On profile, select profile manager...click to groups.
Click add
Make a name
Click - Add 10 channels.
Click color channels - BOOM

Keep in mind this is a clean install,no profiles exist on my machine.

Enclosed is the debug.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.Int32.Parse(String s)
at Vixen.Dialogs.AllChannelsColorDialog..ctor(List`1 channels) in C:\Documents and Settings\KC\My Documents\Visual Studio 2005\Projects\Vixen\Vixen\AllChannelsColorDialog.c s:line 36
at Vixen.Dialogs.ProfileManagerDialog.pictureBoxChann elGroupChannelColors_Click(Object sender, EventArgs e) in C:\Documents and Settings\KC\My Documents\Visual Studio 2005\Projects\Vixen\Vixen\ProfileManagerDialog.cs: line 640
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Vixen
Assembly Version: 2.0.0.14
Win32 Version: 2.0.0.14
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/Vixen.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
AppUpdate
Assembly Version: 2.0.0.9
Win32 Version: 2.0.0.9
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/AppUpdate.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
fmod
Assembly Version: 2.0.0.10
Win32 Version: 2.0.0.10
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/fmod.DLL
----------------------------------------
CometConversion
Assembly Version: 2.0.0.11
Win32 Version: 2.0.0.11
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/AddIns/CometConversion.DLL
----------------------------------------
DMXAddIn
Assembly Version: 2.0.0.11
Win32 Version: 2.0.0.11
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/AddIns/DMXAddIn.DLL
----------------------------------------
MIDIReader
Assembly Version: 2.0.0.11
Win32 Version: 2.0.0.11
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/AddIns/MIDIReader.DLL
----------------------------------------
RemoteClient
Assembly Version: 2.0.0.13
Win32 Version: 2.0.0.13
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/AddIns/RemoteClient.DLL
----------------------------------------
RGBLEDAddIn
Assembly Version: 2.0.0.11
Win32 Version: 2.0.0.11
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/AddIns/RGBLEDAddIn.DLL
----------------------------------------
Spectrum
Assembly Version: 2.0.0.11
Win32 Version: 2.0.0.11
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/AddIns/Spectrum.DLL
----------------------------------------
WattMeter
Assembly Version: 2.0.0.11
Win32 Version: 2.0.0.11
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/AddIns/WattMeter.DLL
----------------------------------------
Waveform
Assembly Version: 2.0.0.13
Win32 Version: 2.0.0.13
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/AddIns/Waveform.DLL
----------------------------------------
LedTriksUI
Assembly Version: 2.0.0.14
Win32 Version: 2.0.0.14
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/Plugins/UI/LedTriksUI.DLL
----------------------------------------
StandardSequence
Assembly Version: 2.0.0.14
Win32 Version: 2.0.0.14
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/Plugins/UI/StandardSequence.DLL
----------------------------------------
TriggerResponse
Assembly Version: 2.0.0.11
Win32 Version: 2.0.0.11
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/Plugins/UI/TriggerResponse.DLL
----------------------------------------
ICSharpCode.SharpZipLib
Assembly Version: 0.85.1.271
Win32 Version: 0.85.1.271
CodeBase: file:///C:/Documents%20and%20Settings/Owner/Desktop/NET/Vixen_2.0_base/ICSharpCode.SharpZipLib.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system>
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

biffklg
06-03-2007, 01:12 AM
I tried it a few times and it didnt happen to me...

Macrosill
06-03-2007, 07:49 AM
I see you have upgraded to 2.0.14. I am not positive but I think that is the latest upgrade and the install requires you to delete a few .dll files. If this is the case did you delete the appropriate files after the upgrade? The files to be deleted can be found in the readme file.

Or I may be totally wrong and have no idea what I am talking about.

Zane
06-03-2007, 10:10 AM
You were using the updated version. You just didn't delete the files. You can find them under notes.txt in the parent directory of Vixen 2.0

A Marchini
06-03-2007, 01:40 PM
You were using the updated version. You just didn't delete the files. You can find them under notes.txt in the parent directory of Vixen 2.0
Actually, it did it before the upgrade. The .DLL files are missing, and shouldn't actually effect anything in this case I imagine.

It could be just chalked up to the ole its because of running service X or because the moon was waxing or watever. However the failure is rather explicit in the code. K.C. might be able to see a potential problem, since he has the source.
It failed somewhere in stringtoNumber. I suppose a debug version could be run that spits out the parameters before this particular call. In any case, K.C. can look at it.

Perhaps I can replicate the problem on another machine , see if my description of steps is correct, that kind of thing.
T.

KC
06-04-2007, 12:27 AM
Thanks, Tony, it's on the list.

KC
06-04-2007, 01:14 AM
The answer to this may be helpful to others who end up using the alpha version of 2.0.

When it's upgrading from 2.0.0.12 to 2.0.0.13, it runs a conversion on your data. One of the conversion pieces is to add some information for persisting the color dialog's custom colors (such as when you clicked the channel color button). However, there is a bug in that conversion that will cause it to fail part-way through. It assumes the preferences file exists, which it doesn't if you haven't run the application. Short story long: it never gets a chance to add that color data.

Workaround: After you unzip the files and run the application for the first time, do not let it upgrade. Let the application start, then close it. This will create the preference file. Then that conversion will have something to put the color data into.

Macrosill
06-04-2007, 08:12 AM
How do you "not let it upgrade"? Isn't it automatic? I know about the "no updates" file but other may not and is that the only way?

KC
06-04-2007, 10:43 AM
It will prompt you when you start the application. When it asks if you want to upgrade, you say "no".

Macrosill
06-04-2007, 11:15 AM
I must be blind, I do not remember seeing that screen. Time for new glasses! :lol: