Important: These forums are for discussions between SkyDemon users. They are not routinely monitored by SkyDemon staff so any urgent issues should be sent directly to our Customer Support.

Upgrade from 1.3.1 to 1.3.2


Author
Message
LUFTY
LUFTY
Too Much Forum (1.6K reputation)Too Much Forum (1.6K reputation)Too Much Forum (1.6K reputation)Too Much Forum (1.6K reputation)Too Much Forum (1.6K reputation)Too Much Forum (1.6K reputation)Too Much Forum (1.6K reputation)Too Much Forum (1.6K reputation)Too Much Forum (1.6K reputation)
Group: Forum Members
Posts: 15, Visits: 65
Hi TIm

I have done an in place upgrade from 1.3.1 to 1.3.2 and I know get an Unhandled Exception Error when first running the application as follows :-

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

************** Exception Text **************
System.ArgumentException: An item with the same key has already been added.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at Divelements.Aviation.EntityData.Managers.AerodromeManager.EntitiesAdded(IEnumerable`1 entities)
   at Divelements.Mapping.Managers.SpotEntityManager`1.AddRange(IEnumerable`1 entities)
   at Divelements.Mapping.Managers.PackagedSpotEntityManager`1.Add(EntityPackage`1 package)
   at Divelements.Aviation.DataManager.<>c__DisplayClass19.<GenerateAddDataDelegate>b__f(Object , EventArgs )
   at Divelements.Aviation.DataManager.<>c__DisplayClass8.<EnqueueQueue>b__7(Object , EventArgs )
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
SkyDemon
    Assembly Version: 1.3.2.18776
    Win32 Version:
    CodeBase: file:///C:/Program%20Files/Divelements%20Limited/SkyDemon/SkyDemon.exe
----------------------------------------
Divelements.Aviation
    Assembly Version: 1.0.3838.18774
    Win32 Version: 1.0.3838.18774
    CodeBase: file:///C:/Program%20Files/Divelements%20Limited/SkyDemon/Divelements.Aviation.DLL
----------------------------------------
Divelements.SandGrid
    Assembly Version: 2.2.3.1
    Win32 Version: 2.2.3.1
    CodeBase: file:///C:/Program%20Files/Divelements%20Limited/SkyDemon/Divelements.SandGrid.DLL
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    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.4927 (NetFXspW7.050727-4900)
    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.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
SandDock
    Assembly Version: 3.0.6.1
    Win32 Version: 3.0.6.1
    CodeBase: file:///C:/Program%20Files/Divelements%20Limited/SkyDemon/SandDock.DLL
----------------------------------------
Divelements.Mapping
    Assembly Version: 1.0.3838.18774
    Win32 Version: 1.0.3838.18774
    CodeBase: file:///C:/Program%20Files/Divelements%20Limited/SkyDemon/Divelements.Mapping.DLL
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
SandBar
    Assembly Version: 1.4.3.1
    Win32 Version: 1.4.3.1
    CodeBase: file:///C:/Program%20Files/Divelements%20Limited/SkyDemon/SandBar.DLL
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.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.

This running under Windows 7 32 Bit.

Regards

Lufty

Reply
pmh
pmh
Too Much Forum (1.4K reputation)Too Much Forum (1.4K reputation)Too Much Forum (1.4K reputation)Too Much Forum (1.4K reputation)Too Much Forum (1.4K reputation)Too Much Forum (1.4K reputation)Too Much Forum (1.4K reputation)Too Much Forum (1.4K reputation)Too Much Forum (1.4K reputation)
Group: Forum Members
Posts: 17, Visits: 43
Thanks for the answer.

It is clear for me the two data sets are in conflict. What kind of name convetion do I need to follow not to have this to happen again? I thought the custom data was given special names to avoid risk of overlap.

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Reading This Topic

Login

Explore
Messages
Mentions
Search