The thread 0x18ac has exited with code 259 (0x103).
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Users\Pwnyhofpl0x\Desktop\Snowl-LegendaryClient-5e620d7\Snowl-LegendaryClient-5e620d7\LegendaryClient\bin\Debug\LegendaryClient. exe'. Symbols loaded.
Step into: Stepping over non-user code 'LegendaryClient.App..ctor'
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System .Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\Syst em.Configuration.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Step into: Stepping over non-user code 'LegendaryClient.App.Main'
Step into: Stepping over non-user code 'LegendaryClient.App.InitializeComponent'
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Users\Pwnyhofpl0x\Desktop\Snowl-LegendaryClient-5e620d7\Snowl-LegendaryClient-5e620d7\LegendaryClient\bin\Debug\MahApps.Metro.dl l'. Module was built without symbols.
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Users\Pwnyhofpl0x\Desktop\Snowl-LegendaryClient-5e620d7\Snowl-LegendaryClient-5e620d7\LegendaryClient\bin\Debug\jabber-net.dll'. Cannot find or open the PDB file.
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Users\Pwnyhofpl0x\Desktop\Snowl-LegendaryClient-5e620d7\Snowl-LegendaryClient-5e620d7\LegendaryClient\bin\Debug\PVPNetConnect.dl l'. Cannot find or open the PDB file.
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Access ibility\v4.0_4.0.0.0__b03f5f7f11d50a3a\Accessibili ty.dll'. Cannot find or open the PDB file.
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Presen tationFramework.Aero\v4.0_4.0.0.0__31bf3856ad364e3 5\PresentationFramework.Aero.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_32\System.W eb\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.dll'. Cannot find or open the PDB file.
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Users\Pwnyhofpl0x\Desktop\Snowl-LegendaryClient-5e620d7\Snowl-LegendaryClient-5e620d7\LegendaryClient\bin\Debug\System.Windows.I nteractivity.dll'. Cannot find or open the PDB file.
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Presen tationFramework-SystemXml\v4.0_4.0.0.0__b77a5c561934e089\Presentat ionFramework-SystemXml.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\UIAuto mationTypes\v4.0_4.0.0.0__31bf3856ad364e35\UIAutom ationTypes.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Presen tationFramework.resources\v4.0_4.0.0.0_de_31bf3856 ad364e35\PresentationFramework.resources.dll'. Module was built without symbols.
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Users\Pwnyhofpl0x\Desktop\Snowl-LegendaryClient-5e620d7\Snowl-LegendaryClient-5e620d7\LegendaryClient\bin\Debug\SharpZipLib.dll' . Cannot find or open the PDB file.
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Presen tationCore.resources\v4.0_4.0.0.0_de_31bf3856ad364 e35\PresentationCore.resources.dll'. Module was built without symbols.
System.Windows.Data Error: 3 : Cannot find element that provides DataContext. BindingExpression

no path); DataItem=null; target element is 'Button' (Name='HomeButton'); target property is 'NoTarget' (type 'Object')
System.Windows.Data Error: 3 : Cannot find element that provides DataContext. BindingExpression

no path); DataItem=null; target element is 'Button' (Name='PlayButton'); target property is 'NoTarget' (type 'Object')
System.Windows.Data Error: 3 : Cannot find element that provides DataContext. BindingExpression

no path); DataItem=null; target element is 'Button' (Name='ProfileButton'); target property is 'NoTarget' (type 'Object')
System.Windows.Data Error: 3 : Cannot find element that provides DataContext. BindingExpression

no path); DataItem=null; target element is 'Button' (Name='ShopButton'); target property is 'NoTarget' (type 'Object')
System.Windows.Data Error: 3 : Cannot find element that provides DataContext. BindingExpression

no path); DataItem=null; target element is 'Button' (Name='SettingsButton'); target property is 'NoTarget' (type 'Object')
System.Windows.Data Error: 3 : Cannot find element that provides DataContext. BindingExpression

no path); DataItem=null; target element is 'Button' (Name='LogoutButton'); target property is 'NoTarget' (type 'Object')
'LegendaryClient.vshost.exe' (CLR v4.0.30319: LegendaryClient.vshost.exe): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\UIAuto mationProvider\v4.0_4.0.0.0__31bf3856ad364e35\UIAu tomationProvider.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The thread 0x15e8 has exited with code 259 (0x103).
System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='TransparentWhiteBrush'
System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='VerticalScrollBar'
System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='VerticalScrollBar'
System.Windows.ResourceDictionary Warning: 9 : Resource not found; ResourceKey='TransparentWhiteBrush'
The thread 0x1b3c has exited with code 259 (0x103).
The thread 0x18a0 has exited with code 259 (0x103).
The thread 0x1be8 has exited with code 259 (0x103).
The thread 0x184c has exited with code 259 (0x103).