If you get the following error when using the Microsoft.ApplicationBlocks.ExceptionManagement library: System.Security.SecurityException: The event source ExceptionManagerInternalException does not exist and cannot be created with the current permissions. ---> System.Security.SecurityException: Requested registry access is not allowed. at System.ThrowHelper.ThrowSecurityException(ExceptionResource resource) at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable) at System.Diagnostics.EventLog.CreateEventSource(EventSourceCreationData sourceData) at System.Diagnostics.EventLog.CreateEventSource(String source, String logName) at Microsoft.ApplicationBlocks.ExceptionManagement.DefaultPublisher. VerifyValidSource() One way of solving this is to install the Microsoft.ApplicationBlocks.ExceptionManagement.dll by running the following in a dos window: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe Microsoft.ApplicationBlocks.Exception
Was updating a MS Word 2010 document and coming from a WordPerfect background I like to see the formatting text when I'm editing. A quick search found this: http://answers.microsoft.com/en-us/office/forum/office_2010-word/view-hidden-text/0db765e8-0f42-476e-88dc-267eccdbf45b That pointed me in the right direction. You click on the File tab then click Options . On the Word Options dialog click on the Display option on the left menu bar. Then check the "Show all formatting marks" checkbox. Like this: Or if you only want to see specific formatting marks you can pick and choose between "Tab characters", "Spaces", "Paragraph marks", "Hidden text", "Optional hyphens", and "Object anchors".
When I started experimenting with TDD and specifically writing the test first, I had a sudden realization as I began to contemplate where should I place this new test I was about to create. I realized that the simplest place for the test would be in a folder structure that matched the UI for a web app or the API for a web API, and then quickly realized it would be helpful to have the production code folder structure match as well. I had been working on several large complex code bases, some web apps, and some web APIs, and trying to find the code that needed to change or where to add new code wasn't obvious from the code organization. The code was organized in the layered architecture style with UI layer, Service Layer, Repository Layer, etc. kind of like the structure Microsoft uses in "Traditional N-Layer architecture applications" . With folders for Controllers, Views, ViewModels, etc. This architecture-oriented code organization(AOCO) is really good at telling you