This is where our experts try to teach you the very flexible modding system for our previous release - SOW Gettysburg and its add-ons. It's powerful, but dangerous. Post your tips and your questions.
I just checked to make sure that (win 7) the Netframework 4.0 is active, and the previous version is disabled (system services). Hmmmm, LP, can you check your services, and see if your Net Framework 4 is enabled, and the previous version is disabled...if you can or willing could you let me know please. This is very peculiar.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at DevComponents.DotNetBar.Validator.Highlighter.UpdateHighlightPanelBounds()
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnSizeChanged(EventArgs e)
at System.Windows.Forms.Control.UpdateBounds(Int32 x, Int32 y, Int32 width, Int32 height, Int32 clientWidth, Int32 clientHeight)
at System.Windows.Forms.Control.UpdateBounds()
at System.Windows.Forms.Control.WmWindowPosChanged(Message& m)
at System.Windows.Forms.Control.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)
************** 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.
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.
Hmmmm, Okay I'm going to install VMware, install a fresh copy of Windows XP, and Windows 7, and I'm going to try to narrow this thing down. Sometimes taking the long way around can save time.
I'll let you know what I come up with, if anything.
I'm not a programmer here so I have no idea if this could be causing the errors, but it sure looks like it's looking for the editor .exe, and it's just not finding it.
The software doesn't care where he is installed. You can place it where you want, and avoid program files which can be troublesome because of special permission of this directory.
You should have 3 files in the directory :
DevComponents.DotNetBar2.dll
Gettysburg - Scenario Editor.exe
Gettysburg - Scenario Editor.exe.config
the JIT don't give you a stack trace in the details ?
Last edited by Kalliser on Mon Aug 22, 2011 9:10 pm, edited 1 time in total.