Vixen update is erroring out on new computer with XP Pro

[JEEPGUY]

I have been trying to load Vixen on one of my other computers. I am able to successfully load and run Vixen 2.05, however, when I try to load the updates it runs through the updates 2.051 to 2.09, allows me to view the notes and then the Microsoft.net framework pops up and indicates unhandled exception has occurred in your application. Here's the details:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at Update.Form1.Form1_FormClosing(Object sender, FormClosingEventArgs e)
at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(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)

************** 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
----------------------------------------
Update
Assembly Version: 2.0.5.1
Win32 Version: 2.0.5.1
CodeBase: file:///C:/Downloads/Vixen 2.0 Release/Vixen 2.0 Release/Update.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_MSI....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
----------------------------------------
ICSharpCode.SharpZipLib
Assembly Version: 0.85.1.271
Win32 Version: 0.85.1.271
CodeBase: file:///C:/Downloads/Vixen 2.0 Release/Vixen 2.0 Release/ICSharpCode.SharpZipLib.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSI....0__b03f5f7f11d50a3a/System.Configuration.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
----------------------------------------
************** 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.windows.forms jitDebugging="true" />
</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.



I have tried 3 times.

I currently running Vixen on the PC I have been programming on without any problems. I am running Win XP on that computer.

I am running Win XP Pro on the one that is my show computer that Vixen won't load correctly. Both are P4's.

Please let me know if you have any suggestions.

 

[cgarwood]

I had the same problem on my show machine. Only solution i could figure out was to downgrade Vixen.

 

[JEEPGUY]

That's what I did. Down to 2.05.

KC, any idea why the updates are erroring? Could it be .net Framework?

 

[RavingLunatic]

KC wants to have all bugs/problems reported on the Vixen Bugzilla site. KC wants to use that for starting and tracking Vixen "bug" reports. He probably won't be checking in this forum for new issues.


More info:
http://www.doityourselfchristmas.com...ead.php?t=4846

 

[omzig]

Where can I get version 2.05 now?

EDIT: Nevermind...I got it.