Open Dental Forum

I have a problem with the latest SigPlusNET.dll when I try to r:un 7.9.19 or 11.0.x (I think it was just added today)?

I've tried remaking the references but I get the same error.


System.IO.FileLoadException was unhandled
Message=Could not load file or assembly 'SigPlusNET, Version=1.0.2245.36238, Culture=neutral, PublicKeyToken=6aef07010bb0624f' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Source=CodeBase
FileName=SigPlusNET, Version=1.0.2245.36238, Culture=neutral, PublicKeyToken=6aef07010bb0624f
FusionLog==== Pre-bind state information ===
LOG: User = TigerBook\wjs
LOG: DisplayName = SigPlusNET, Version=1.0.2245.36238, Culture=neutral, PublicKeyToken=6aef07010bb0624f
(Fully-specified)
LOG: Appbase = file:///C:/Users/wjs/Desktop/ODVersions/opendental7.9b/opendental7.9/OpenDental/bin/Release/
LOG: Initial PrivatePath = NULL
Calling assembly : CodeBase, Version=7.1.0.0, Culture=neutral, PublicKeyToken=null.
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Users\wjs\Desktop\ODVersions\opendental7.9b\opendental7.9\OpenDental\bin\Release\OpenDental.vshost.exe.Config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Post-policy reference: SigPlusNET, Version=1.0.2245.36238, Culture=neutral, PublicKeyToken=6aef07010bb0624f
LOG: Attempting download of new URL file:///C:/Users/wjs/Desktop/ODVersions/opendental7.9b/opendental7.9/OpenDental/bin/Release/SigPlusNET.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Minor Version
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.

StackTrace:
at CodeBase.TopazWrapper.ClearTopaz(Control topaz)
at Anesthesia.FormAnestheticRecord.ClearSigBox()
at Anesthesia.FormAnestheticRecord.butAddAnesthetic_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at OpenDental.UI.Button.OnClick(EventArgs ea) in C:\Users\wjs\Desktop\ODVersions\opendental7.9b\opendental7.9\OpenDental\UI\Button.cs:line 153
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.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.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.RunDialog(Form form)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()
at Anesthesia.FormOpenDentalA.menuItemAnestheticRecord_Click(Object sender, EventArgs e)
at System.Windows.Forms.MenuItem.OnClick(EventArgs e)
at System.Windows.Forms.MenuItem.MenuItemData.Execute()
at System.Windows.Forms.Command.Invoke()
at System.Windows.Forms.Command.DispatchID(Int32 id)
at System.Windows.Forms.Control.WmCommand(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(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.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at OpenDental.ProgramEntry.Main(String[] args) in C:\Users\wjs\Desktop\ODVersions\opendental7.9b\opendental7.9\OpenDental\Main Modules\ProgramEntry.cs:line 44
at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException:

OK, NVM.

Had to manually clean the prior version from the /bin folder.

Hello.

I have been trying replacing the library SigPlusNET.dll with a more modern version (ver. 2.0.0.42) looking for resolve some problems. It seems to work ok, but it does not shows previous signatures.
Any suggestions?

Thanks.

David.

There are multitudes of issue with switching how the signatures are generated, so my guess is that the newer dll might be doing it slightly differently. If the signature control cannot "read" the old signature as valid, it is shown as blank. There are two components to having a correct signature, the signature string that is stored in that database, and the key that is generated by the data the signature is attributed to. If either of those have differed from what they were when they were signed, the signature is considered invalid. On top of that if any settings on the dll generating the signature has changed, or the dll itself works differently there is a good chance it will also be invalidated because of the algorithms used to encrypt the signature string. If that encryption doesn't work the exact same way as it did when it the signature was captured, it will be invalid.

That being said, there were also several issues with signatures keys being invalidated over versions due to the way new line characters were stored. This is especially prevalent when using middle tier. Most of these bugs have been fixed in past versions (allow both /r/n and /n as valid new line characters in the key), but I also fixed a lot of the issues for topaz pads in 16.1 that had not already been fixed.

Tl:Dr; Changing the dll version can invalidate any signatures captured in the past (using a different dll).