Troubleshooting Silverlight sllauncher

[Izna]

Does sllauncher mark a number of suggestions inside Windows Event Log in case of problems? I run my application inside Windows 7 through "sllauncher /emulate" and I contain one case while the silverlight doesn't launch in any way. No indications, no exceptions, no log not anything. I erased the Windows 7 User Profile and formed it all over again and the identical Silverlight worked as anticipated. Should I need to make use of sysinternal "Process Monitor" to discover the sllauncher issues otherwise will the sllauncher writes inside EventLog?

[Galbraith]

Generate a fresh profile on the PC and make sure if the problem perseveres. You can generate split accounts for every being that will be using the PC. This permits each user to contain their personal file folders as well as settings for instance the wallpaper, Start menu, visual method, and so on. You can generate and arrange user accounts through the User Accounts tool inside Control Panel. To release the User Accounts tool, Go to the Control Panel from the Start menu, and afterward double on top of click User Accounts icon.

[MaggieK]

Silverlight utilizes the sllauncher.exe utility in order to install, run, and uninstall out-of-browser apps or programs. Furthermore, Visual Studio 2010 makes use of this tool to run out-of-browser apps into emulation approach to facilitate debugging. You will not characteristically employ this tool straightforwardly except you require performing several error handling dealings within custom scripts.

[GracieSingh]

The error messages are primarily pertinent if you make use of the JavaScript API method for error handling (OnError) otherwise for universal script-level debugging for the duration of improvement. The error messages may not be applicable to manage user code exemption handling through the UnhandledException occasion. Though, in numerous cases, native errors can happen while you create managed calls to users that make use of functionality within the core. The native errors may be helpful debugging hints for the period of the development stage to conclude what feature of the managed call is not functioning as projected.

[Sydney_7]

The Silverlight managed API has a supervised level of error handling as well as exception handling that hush-up the runtime that processes your app code. So as to hold exceptions that create from your app's user code, you can register a handler intended for UnhandledException. Platform code exceptions, and exceptions that you select not to hold through UnhandledException, are approved on to the native/unmanaged error system within the Silverlight plug-in. By the side of this level, you can process the errors by the use of OnError handler that is precised for the period of plug-in instantiation.

[Radames]

The Silverlight error/exception system creates a dissimilarity among platform exceptions (exceptions that are applicable to the APIs that Silverlight executes for its personal.NET library and core run time), and exceptions that are the consequence of executing an app's code during the core run time. Platform exceptions must be uncommon, except if they occur, they commonly overthrow the Silverlight core, and are not at all recoverable.