Prerequisites
- Compiling the Silverlight 3 project requires the Silverlight 3 SDK.
- Compiling the Silverlight 4 project requires the Silverlight 4 SDK.
- Compiling the Windows Phone 7 project requires the Windows Phone 7.0 Tools RTM or the Windows Phone SDK (Beta 2).
- Compiling the server-side project requires NuGet 1.4 or later.
Installation Notes
The server-side component is required, even for the Windows Phone version.
This preview does not cache the Log data locally and send the data when an application exists, like the standard Agent does. It requires real-time communication between the Client and the Server. This may have an adverse effect on your phone connection. It is recommended that you notify your users that this app may consume data while the app is active.
The Client will stop attempting to contact the Server after 3 failed requests.
After three failed attempts to connect to the Server, the Client automatically shuts down in a way that doesn't block subsequent Log calls from completing without error. The log message call simply stops storing the log messages, in order to prevent further memory consumption. There is currently no way to re-activate the Client from within a session, but we will be improving and refining this mechanism in future releases.
For the best experience, IIS Dynamic Compression is highly recommended.
The Client automatically attempts to compress all communication. In order to save bandwidth for your users, it is highly recommended that you enable dynamic compression on your IIS installation for "application/xml" requests.
If modifying the code is not required, installing the packages from NuGet provides the simplest experience.
We've done some extra work to minimize the effort needed to coordinate dependencies, and eliminating the need to register the WCF routes in the Global.asax file. If you're not yet familiar with NuGet, it's easy, and it integrates with Visual Studio 2010. For more information, see the
NuGet Package Manager in the Visual Studio Gallery.