I have an UWP application which is working fine on various machines but on one particular machine, it is crashing silently.
When I debugged the installed app through visual studio I figured out that it is not getting the resources on the XAML file e.g
{ThemeResource ComboBoxDropdownContentMargin}
{Binding TemplateSettings.DropDownContentMinWidth, RelativeSource={RelativeSource Mode=TemplatedParent}}
The Output window is showing the following exception
Exception thrown at 0x751641E8 (KernelBase.dll) in
myapplicationnamechanged
.exe: 0x40080201: WinRT originate error
(parameters: 0x80004005, 0x00000046, 0x05CDC7A8). Exception thrown at
0x751641E8 (KernelBase.dll) in Infonet.CStoreCommander.UI.exe:
0x40080201: WinRT originate error (parameters: 0x802B000A, 0x0000005C,
0x05CDC73C).
120|2018-11-28T14:45:50.1043744+00:00|INFO|2|App|.UnhandledExceptionHandler
line:59 Unhandled Exception -->
Windows.UI.Xaml.Markup.XamlParseException: The text associated with
this error code could not be found.
Cannot find a Resource with the Name/Key ComboBoxDropdownContentMargin
[Line: 0 Position: 0] Unhandled exception at 0x0F7F2DEB
(Windows.UI.Xaml.dll) in Infonet.CStoreCommander.UI.exe: 0xC000027B:
An application-internal exception has occurred (parameters:
0x116F1BA8, 0x00000004).
As per this MSDN documentation ComboBoxDropdownContentMargin was made availalbe from Windows 10, Version 1511 (Windows SDK version 10.0.10586.0).
So if you are running your App which has Version lower than the supported version, in that case, it will throw an exception.
Related
So, I made a fresh ASP.NET Core Web App (Model-View-Controller) project in visual studio 2022 and .NET 6 like shown below.
When I start the project (without changing anything) I get the following 3 exceptions:
Exception thrown: 'System.IO.IOException' in System.Net.Security.dll
Exception thrown: 'System.IO.IOException' in System.Private.CoreLib.dll
Exception thrown: 'System.IO.IOException' in System.Private.CoreLib.dll
However the project still runs and the website opens as expected.
Are these exceptions something to worry about?
The fact that an exception is thrown is not a problem. Exceptions get thrown. That's what they do. It's a problem when they aren't caught and managed appropriately. If your code isn't even seeing those exceptions then they are being caught and handled in system code, so they're not relevant to you. If your application crashes, that is an unhandled exception, so you need to look at why it's being thrown and whether or not you need to prevent it and/or catch it and clean up.
I've created an android app via Xamarin. the app is supposed to connect to sql server through an asmx webservice. I've tested the asmx in my browser and it works well. but the problem is that when I try the app on my android device (not emulator), the following exception occurs:
system.reflection.targetinvocationexception: 'an exception occurred during the operation, making the result invalid. check innerexception for exception details.'.
now there is a warning that I got after I built my project and it is as follows:
warning XA0105: The $(TargetFrameworkVersion) for System.EnterpriseServices (v10.0) is greater than the $(TargetFrameworkVersion) for your project (v9.0). You need to increase the $(TargetFrameworkVersion) for your project.
so i'm guessing the exception is due to this warning. I tried increasing the target framework of my project but I got more warnings and errors because api level 29 of the new target framework doesn't seem available. so my question is, is the exception truly the result of the warning? if not what is the solution for such a warning?
Attempting to deploy a UWP Windows app in master mode throws an unhandled exception as follows:
Unhandled exception at 0x603FF073 (Windows.UI.Xaml.dll) in
HopTheBall.exe: 0xC000027B: An application-internal exception has
occurred (parameters: 0x038C1FB0, 0x00000002).
Can anyone give the rectification for this error?
I create a new C# Windows Form project in Visual Studio 2013 Update 5. I do not change it in any way. It debugs properly as usual. As soon as I change the Platform target to x64, the debugger shows this error:
System.AccessViolationException was unhandled
Message: An unhandled exception of type 'System.AccessViolationException' occurred in System.Windows.Forms.dll
Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
This happens in every 5 times of debugging. Do you have any idea on what may be causing this error and how it can be fixed?
I have a WCF project (.NET 4.5) and when I call a long running function on it, I'm getting this error:
A first chance exception of type 'System.IndexOutOfRangeException' occurred in mscorlib.dll
in the output window, but the thing is when I debug the project, there are no exceptions thrown in the project and the project keeps running/debugging as if no error happened. I thought that if there was an exception in my code, it should break and show the stack trace, but in this case no errors and keeps running. I'm seeing this information like a lot. It fills the output window and keeps going/adding
Do anyone know what this error means? Why am I not getting unhandled exception thrown error if this is true?