for some reason i get a "Microsoft .NET Framework" error when ever i copy past in Adobe programs, here is 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.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.Collections.ArrayList.get_Item(Int32 index)
at PluginClipboard.ClipboardData.<.ctor>b__2(DataObject o)
at PluginClipboard.ClipboardData..ctor(IDataObject dataObject)
at PluginClipboard.ClipboardViewer.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
InputText
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/adam/AppData/Roaming/Rainmeter/Plugins/NXTInput.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
PluginClipboard
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/adam/AppData/Roaming/Rainmeter/Plugins/PluginClipboard.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.
It is currently April 26th, 2024, 8:41 am
unhandled exception has occurred in your application
-
- Posts: 1
- Joined: February 9th, 2017, 2:19 pm
-
- Developer
- Posts: 522
- Joined: March 2nd, 2016, 6:23 pm
Re: unhandled exception has occurred in your application
This seems to be an issue with PluginClipboard ( i assume it's this one: https://forum.rainmeter.net/viewtopic.php?f=18&t=10075, but i'm not certain)shikuru wrote:for some reason i get a "Microsoft .NET Framework" error when ever i copy past in Adobe programs, here is the details:
A lot of error text...
As zzeneg has not been online for about a year do i doubt that it'll be fixed since he hasn't provided the necessary code.
This is therefore not a issue that can easily be fixed :/ (Since the plugin in question is external)
From the error report do i assume that it is nxt-os causing the issue, but i cannot be certain. My best clue would be to give him this error report so that he can fix this error for his skin
-
- Developer
- Posts: 2684
- Joined: November 24th, 2011, 1:42 am
- Location: Utah
Re: unhandled exception has occurred in your application
This could also be the issue as well. I believe this is a modified version of our InputText plugin.shikuru wrote:InputText
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/adam/AppData/Roaming/Rainmeter/Plugins/NXTInput.DLL
Like theAzack9 said, these are 3rd party plugins and we really can't help much to remedy the problem(s). Contacting the skin author and plugin authors is the way to go with this.
-Brian