Silverlight Integration Pack
Greetings, Silverlight line-of-business application developers!
Based on the feedback we’ve received in the early stages of planning through emails, blogs, events, a round of consultation with our advisors and our own spikes, here’s the list of the stories. You will see those posted by Producer, but they actually came from users. Now it’s your time to vote to help us determine what will go in the release of the Enterprise Library 5.0 Silverlight Integration Pack.
If you don’t see a scenario you care about on the list, feel free to suggest it.
Please note this list may not always represent the actual priority list for the patterns & practices development team. It also does not constitute any commitments.
Also, check out the community page (http://entlib.codeplex.com/wikipage?title=EntLib5Silverlight) with links to preview code drops, demos of the stories implemented and screencasts.
-
Logging through a service: client side component, pull
Provide me with an "upload-to-service" client side component, which could receive upload requests from the server.
60 votes -
Client-side logging to a file (in out of browser scenario)
I want my log messages to be written to a file in the file system on the local system.
15 votes -
Logging through Azure queue quickstart
I want to have an easy way of logging through an Azure queue. Provide service side boilerplate code that I can reuse.
13 votes -
Auditing support
Also provide quickstart for enabling of logging/tracing all user dialogs (when audit trail of user interactions is required or for security reasons). Note: this has reliability implications that must be considered. The philosophy of the logging block is "do not affect the app even in the presence of a catastrophic logging failure". However, for this specialized scenario this would need to be changed.
10 votes -
Multicast logging
I want to write log messages to a UDP console sink.
5 votes -
Persisting logging block configuration changes
I want to persist logging config changes at run time on the same machine
4 votes -
Limited configuration of client-side logging through page-level params
The verbosity level can be adjusted manually by using page-level parameters (no UI)
4 votes
- Don't see your idea?
