|
PROFESSIONAL NEWSGROUPS WINDEV, WEBDEV and WINDEV Mobile |
| | | | | |
Home → WINDEV 2024 → [WD19]-[WD21] Crash after installation of Windows 10 Anniversary Update (1607) when using .Net library |
[WD19]-[WD21] Crash after installation of Windows 10 Anniversary Update (1607) when using .Net library |
Started by Peter VC, Sep., 22 2016 2:59 PM - 4 replies |
| |
| | | |
|
| |
Posted on September, 22 2016 - 2:59 PM |
We use Windev 19 (but we've tested it in WD21 as well and it's the same problem). We use an external .Net library for integration of encrypted communication with health-related web services, this communication is authenticated using the electronic identity card of the user who has to enter their pin-code. Since the installation of Windows 10 Anniversary Update (1607), our windev program crashes without giving an exception or an error in WinDev. When we view the information of the crash in the event log of Windows, we can see that it crashes in the Windows.UI.Xaml.dll (which is a new dll in this version of Windows 10, the previous version of Windows 10 did not have this). When we use the .Net library from a .Net program (command line style or GUI style), it works fine. When we use the .Net library from a WinDev program, it crashes, presumably when trying to display the pin-code screen. We wrote part of the .Net library ourselves, but not the part that reads the smartcard and shows the pin-code entry screen.
Since it's GUI related, we've tried several things: put a XAML component in our WinDev screen (maybe it initializes XAML?), use a .Net form in our .Net library and give it our Windev screen as parent. Doesn't work. And I hate to now be forced to extract our nicely integrated solution in a separate program just because of some change by Microsoft...
Name of module with error: Windows.UI.Xaml.dll, version: 10.0.14393.187, timestamp: 0x57cf9c3e Exception code: 0xc000027b Error margin: 0x008b7a98 Id van proces met fout: 0x16ec Path to module with error: C:\Windows\System32\Windows.UI.Xaml.dll Rapport-id: e9f72afc-e04b-4924-b82b-4d757cdac3b1 Signature of problem: P1: testprogram.exe P2: 1.3.0.11 P3: 573c289a P4: StackHash12_cc4 P5: 0.0.0.0 P6: 00000000 P7: 80004005 P8: 0
Any clues? Greetings. |
| |
| |
| | | |
|
| | |
| |
Posted on September, 22 2016 - 3:38 PM |
Hi Peter,
clearly, you are not alone and windev is not the only one with the problem
Just google Windows.UI.Xaml.dll crash and you'll see...
by example: http://answers.microsoft.com/en-us/windows/forum/apps_windows_10-winapps/windows-10-facebook-crashes-with-chat/9d25c61b-ee1d-4d99-a992-ada08d94a337…
Best regards
-- Fabrice Harari International WinDev, WebDev and WinDev mobile Consulting
Ready for you: WXShowroom.com, WXReplication (open source) and now WXEDM (open source)
More information on http://www.fabriceharari.com
Le 9/22/2016 à 6:59 AM, Peter VC a écrit :
We use Windev 19 (but we've tested it in WD21 as well and it's the same problem). We use an external .Net library for integration of encrypted communication with health-related web services, this communication is authenticated using the electronic identity card of the user who has to enter their pin-code. Since the installation of Windows 10 Anniversary Update (1607), our windev program crashes without giving an exception or an error in WinDev. When we view the information of the crash in the event log of Windows, we can see that it crashes in the Windows.UI.Xaml.dll (which is a new dll in this version of Windows 10, the previous version of Windows 10 did not have this). When we use the .Net library from a .Net program (command line style or GUI style), it works fine. When we use the .Net library from a WinDev program, it crashes, presumably when trying to display the pin-code screen. We wrote part of the .Net library ourselves, but not the part that reads the smartcard and shows the pin-code entry screen.
Since it's GUI related, we've tried several things: put a XAML component in our WinDev screen (maybe it initializes XAML?), use a .Net form in our .Net library and give it our Windev screen as parent. Doesn't work. And I hate to now be forced to extract our nicely integrated solution in a separate program just because of some change by Microsoft...
Name of module with error: Windows.UI.Xaml.dll, version: 10.0.14393.187, timestamp: 0x57cf9c3e Exception code: 0xc000027b Error margin: 0x008b7a98 Id van proces met fout: 0x16ec Path to module with error: C:\Windows\System32\Windows.UI.Xaml.dll Rapport-id: e9f72afc-e04b-4924-b82b-4d757cdac3b1 Signature of problem: P1: testprogram.exe P2: 1.3.0.11 P3: 573c289a P4: StackHash12_cc4 P5: 0.0.0.0 P6: 00000000 P7: 80004005 P8: 0
Any clues? Greetings. |
| |
| |
| | | |
|
| | |
| |
Posted on October, 15 2016 - 11:00 AM |
Hello,
WD17 when i try to generate the executable of my program, Windev stopped working.
When I look in the windows log, I see that it is also related to the Windows.Ui.Xaml.Dll file
Problems started with the anniversary update of Windows 10.
Anyone knows a solution ?
Thx. |
| |
| |
| | | |
|
| | |
| |
Posted on February, 10 2017 - 5:46 PM |
Bonjour,
Nous avons aussi le problème avez vous une solution.
Merci |
| |
| |
| | | |
|
| | |
| |
Posted on February, 16 2017 - 10:46 AM |
Même problème lors de l'appel d'un webservice sécurisé avec carte à puce : La fenêtre de code PIN du middleware ne s'affiche jamais. Windev tourne en boucle. |
| |
| |
| | | |
|
| | | | |
| | |
| | |
| |
|
|
|