StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow to log in UTF-8 using EnterpriseLibrary.Logging
primarykey
Id
15497200
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-19T10:40:54.957
FavoriteCount
0
LastActivityDate
2014-09-23T01:56:46.833
LastEditDate
2014-09-23T01:56:46.833
LastEditorUserId
1505120
OwnerUserId
2186023
ParentId
0
PostTypeId
1
Score
11
ViewCount
1027
LastEditorDisplayName
text
Body
I am kind of stuck with my searches concerning EnterpriseLibrary.Logging. I have a listener and formatter set up like this: <pre><code><add name="NormalLogListener" type="Microsoft.Practices.EnterpriseLibrary.Logging.TraceListeners.RollingFlatFileTraceListener, Microsoft.Practices.EnterpriseLibrary.Logging" listenerDataType="Microsoft.Practices.EnterpriseLibrary.Logging.Configuration.RollingFlatFileTraceListenerData, Microsoft.Practices.EnterpriseLibrary.Logging" fileName="logs/MVC22.log" footer="" formatter="ShortLogFormatter" header="" rollInterval="Day" timeStampPattern="yyyy-MM-dd" maxArchivedFiles="14" /> </code></pre> ... <pre><code><add type="Microsoft.Practices.EnterpriseLibrary.Logging.Formatters.TextFormatter, Microsoft.Practices.EnterpriseLibrary.Logging" template="{timestamp(local)} - {severity} - {category} - {message}" name="ShortLogFormatter" /> </code></pre> I use this in multiple projects and it is working fine. Except for one thing, I want EnterpriseLibrary to create my log file with UTF-8-encoding (I get ANSI files per default), but unfortunately I have no clue how to do that. I have special characters in strings that I want to be able to log into my file (such as umlauts); I see the logging works fine, when I convert my file to UTF-8 and let it be used further, but I really want to have it created that way. Can this be done in the xml configuration or somewhere else? Thanks for any help in advance!
Tags
<c#><logging><encoding><enterprise-library-5>
Title
How to log in UTF-8 using EnterpriseLibrary.Logging
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USpnuts
UserOwnerUserId
1. USDrCopyPaste
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHow to log in UTF-8 using EnterpriseLibrary.Logging
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POHow to log in UTF-8 using EnterpriseLibrary.Logging
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POHow to log in UTF-8 using EnterpriseLibrary.Logging
 UserUserId
 USDrCopyPaste
 VoteTypeVoteTypeId
 VTBountyStart
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.