Reply to thread

Message

<blockquote data-quote="Mr.Mitchell" data-source="post: 13575" data-attributes="member: 10300">Ok, I got some progress for the SEHException.First of all this problem is caused by Visual styles. If the visual styles are disabled the problem does not occur. You can disable these visual styles by commenting the call to Application.EnableVisualStyles(); in Startup.cs in the Mediaportal.Configuration project. The bad thing is that the application loses it's XP look.According to some texts on the internet it should be possible to use Visual styles with an Applicaiotn manifest instead of the call to Application.EnableVisualStyles(). But I got no clue on how make such a manifest. This would probably be the best solution.I did some more research to pinpoint the cause of the problem. I noticed that the exception only occurred when I pressed a button the remote that was mapped to a Key. The exception would NOT occur when I press a key that was mapped to an Action or that was not mapped at all. So it means that the problem only occurs when handling Keys when in the Configuration application.Since I don't see a use to handle keys in the configuration program I decided to &quot;disable&quot; the Handle method when in the Configuration application. I came up with the following workaround.EDIT: Scratch that workaround, it breaks the learning :-(. Going to figure out how to make an application manifest.</blockquote>

[QUOTE="Mr.Mitchell, post: 13575, member: 10300"] Ok, I got some progress for the SEHException. First of all this problem is caused by Visual styles. If the visual styles are disabled the problem does not occur. You can disable these visual styles by commenting the call to Application.EnableVisualStyles(); in Startup.cs in the Mediaportal.Configuration project. The bad thing is that the application loses it's XP look. According to some texts on the internet it should be possible to use Visual styles with an Applicaiotn manifest instead of the call to Application.EnableVisualStyles(). But I got no clue on how make such a manifest. This would probably be the best solution. I did some more research to pinpoint the cause of the problem. I noticed that the exception only occurred when I pressed a button the remote that was mapped to a Key. The exception would NOT occur when I press a key that was mapped to an Action or that was not mapped at all. So it means that the problem only occurs when handling Keys when in the Configuration application. Since I don't see a use to handle keys in the configuration program I decided to "disable" the Handle method when in the Configuration application. I came up with the following workaround. EDIT: Scratch that workaround, it breaks the learning :-(. Going to figure out how to make an application manifest. [/QUOTE]

Verification