Answered by:
Silverlight for Windows Embedded Compact 7 -> Assertion in BlurEffect.dll while loading Application

Question
-
Hi,
i recently started working with Silverlight 3 for Windows Embedded Compact 7.
I first created an Test XAML Project with MS Blend 3 (Project Silverlight for Embedded) and converted it using MS Visual Studio 2005 to an application for smart devices (intelligentes Gerät).
This works so far. Using the debugger the application throws 3 assertions and then the GUI appears. So it seems the BlurEffect.dll, DropShadowEffect.dll and RippleEffect.dll threw those exceptions.
The problem is, I cannot this happens while the application starts and I am not able to step/debug the line/sourcecode where this assertion happens.
So any Ideas on how to solve this Problem would be highly appreciated!
Thx,
Tobias
While the application start, the following dll are loaded:
Modul laden: TestApp.exe
Modul laden: locale.dll
Modul laden: normalize.dll
Modul laden: fpcrt.dll
Modul laden: xamlruntimecore.dll
Modul laden: xmllite.dll
Modul laden: xamlruntime.dll
Modul laden: coredll.dll
CePerf.dll is absent - performance data will not be recorded
Modul laden: xamlrenderplugin.dll
Modul laden: libEGL.dll
Modul laden: libnvrm.dll
Modul laden: libnvos.dll
Modul laden: libnvrm_graphics.dll
Modul laden: libnvwsi.dll
Modul laden: libnvddk_2d_v2.dll
Modul laden: libGLESv2.dll
Modul laden: libnvddk_2d.dll
Modul laden: BlurEffect.dll
*** ASSERTION FAILED in d:\chelanrtm14\private\winceos\coreos\core\corelibc\crtw32\h\tcsncpy_s.inl:53
Buffer is too small
Modul laden: DropShadowEffect.dll
*** ASSERTION FAILED in d:\chelanrtm14\private\winceos\coreos\core\corelibc\crtw32\h\tcsncpy_s.inl:53
Buffer is too small
Modul laden: RippleEffect.dll
*** ASSERTION FAILED in d:\chelanrtm14\private\winceos\coreos\core\corelibc\crtw32\h\tcsncpy_s.inl:53
Buffer is too small
Modul laden: libcgdrv.dll
Modul entladen: libcgdrv.dll
Modul laden: oleaut32.dll
Modul laden: rpcrt4legacy.dll
Modul laden: lpcrt.dll
Modul laden: bcrypt.dll
Modul laden: ole32.dll- Moved by Robert Breitenhofer Tuesday, July 26, 2011 1:22 PM English instead German (From:Silverlight)
Wednesday, July 20, 2011 4:11 PM
Answers
-
Hi Robert,
thanks for response! sadly it didn't help much.
Seems there is a problem with one of the hardware graphics drivers provided by the manufacturer of the board, so no way to fix this problem at the moment.
I found a workaround by editing the registry though:
In
HKEY_LOCAL_MACHINE\XamlRuntime\EffectLibraries\
delete the Keys:
XamlEffect1 = "BlurEffect.dll" XamlEffect2 = "DropShadowEffect.dll" XamlEffect3 = "RippleEffect.dll"
The Silverlight Runtime will therefore ignore the DLLs, when an application is started/loaded.
It's not supposed to be perfect, but it works.
regards
Tobias
- Proposed as answer by Robert Breitenhofer Monday, August 8, 2011 1:04 PM
- Marked as answer by Tobias Holstein Monday, August 8, 2011 1:19 PM
Monday, August 8, 2011 11:26 AM
All replies
-
Hello Tobias Holstein,
Please look at this. Maybe it can help you further:
Configure Virtual CEPC for Silverlight for Windows Embedded Compact 7
Best regards,
Robert
Tuesday, July 26, 2011 1:21 PM -
Hi Robert,
thanks for response! sadly it didn't help much.
Seems there is a problem with one of the hardware graphics drivers provided by the manufacturer of the board, so no way to fix this problem at the moment.
I found a workaround by editing the registry though:
In
HKEY_LOCAL_MACHINE\XamlRuntime\EffectLibraries\
delete the Keys:
XamlEffect1 = "BlurEffect.dll" XamlEffect2 = "DropShadowEffect.dll" XamlEffect3 = "RippleEffect.dll"
The Silverlight Runtime will therefore ignore the DLLs, when an application is started/loaded.
It's not supposed to be perfect, but it works.
regards
Tobias
- Proposed as answer by Robert Breitenhofer Monday, August 8, 2011 1:04 PM
- Marked as answer by Tobias Holstein Monday, August 8, 2011 1:19 PM
Monday, August 8, 2011 11:26 AM -
how do I delete this entries? I don't see them in any *.reg filesFriday, September 9, 2011 1:17 AM
-
This topic really helps! Thank you all!
The path of the related *.reg file is:
C:\WINCE700\public\common\oak\files\common.reg
Another file that may be related is:
C:\WINCE700\public\cebase\oak\misc\winceos.bat
Tuesday, June 4, 2013 8:42 AM -
Hi.
I suppose it is caused by an incorrect parameter passed to wcscpy_s in DLLentry.cpp for BlurEffect, DropShadowEffect and RippleEffect.
Apply the change described below.
// wcsncpy_s( dpCurSettings.lpszName, L"BlurEffect", 32 ); wcsncpy_s( dpCurSettings.lpszName, L"BlurEffect", wcslen(L"BlurEffect") + 1 );
Don't forget to replace the library name string as appropriate.
Tuesday, October 1, 2013 3:00 PM