Skip to content

Commit ec8b7dc

Browse files
committed
Preparation for the new samples browser.
1 parent 9974e43 commit ec8b7dc

File tree

28 files changed

+30
-83
lines changed

28 files changed

+30
-83
lines changed

Diagnostics/PostSharp.Samples.Audit.Extended/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Audit.Extended
2-
31
This example demonstrates how to extend the default Audit logging back-end so that the audit records contains pieces of information that are
42
not provided by the default implementation.
53

Diagnostics/PostSharp.Samples.Audit/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Audit
2-
31
This example shows how to implement audit in a business application.
42

53
Audit records are typically appended to a database and correlated, through a foreign key, to the object entity being accessed and the user performing the operation.

Diagnostics/PostSharp.Samples.Logging.CommonLogging/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Logging.Console
2-
31
This example demonstrates how to configure the PostSharp Logging aspect so that it prints its output to Common.Logging.
42
Here Common.Logging is configured to direct outputs to the system console.
53

Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Logging.Console
2-
31
This example demonstrates how to configure the PostSharp Logging aspect so that it prints its output to the system console.
42

53

Diagnostics/PostSharp.Samples.Logging.CustomBackend.ServiceStack/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Logging.CustomBackend.ServiceStack
2-
31
This example shows how to implement an PostSharp Logging adapter for an arbitraty logging framework. We use the term *back-end* indifferently to mean
42
either the adapter either the target logging framework itself.
53

Diagnostics/PostSharp.Samples.Logging.Customization/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Logging.Customization
2-
31
This example demonstrates several ways to override the default behavior of PostSharp Logging:
42

53
* A value formatter named `FancyIntFormatter`, which demonstrates the implementation of the `Formatter` class.
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Logging.Etw
2-
31
This example demonstrates how to configure the PostSharp Logging aspect so that it prints its output to ETW.
42

53

Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Logging.Log4Net
2-
31
This example demonstrates how to configure the PostSharp Logging aspect so that it prints its output to log4net.
42

53

Diagnostics/PostSharp.Samples.Logging.Loupe/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Logging.Loupe
2-
31
This example demonstrates how to configure the PostSharp Logging aspect so that it prints its output to Loupe from Gibraltar.
42
The application automatically opens an empty window of the Loupe Viewer. You should then see a Loupe desktop notification saying that a new
53
session is available. Click on this notification to open the log, and ignore the empty window that first opened.
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Logging.NLog
2-
31
This example demonstrates how to configure the PostSharp Logging aspect so that it prints its output to NLog.
42

53

Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Logging.Serilog
2-
31
This example demonstrates how to configure the PostSharp Logging aspect so that it prints its output to Serilog.
42

53

Framework/PostSharp.Samples.Authorization/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Authorization
2-
31
This example demonstrates how to enforce a non-trivial security model with aspect-oriented programming.
42

53
The `PostSharp.Samples.Authorization.Framework` defines the skeleton of an abstract security model. The key concept is represented the `IPermission` interface, with typical

Framework/PostSharp.Samples.AutoDataContract/README.md

+1-3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,4 @@
1-
# PostSharp.Samples.AutoDataContract
2-
3-
When you have a large object model, annotating it for the WCF serializer (`DataContractFormatter`)
1+
When you have a large object model, annotating it for the WCF serializer (`DataContractFormatter`)
42
can be tedious. All classes and derived classes need to be annotated with the `[DataContract]` custom
53
attribute, and all properties need the `[DataMember]` custom attribute. If you forget a single `[DataMember]`
64
attribute, no build-time error or run-time will occur, but your program will behave incorrectly and the

Framework/PostSharp.Samples.AutoRetry/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.AutoRetry
2-
31
The `AutoRetry` aspect, when applied to a method, retries the execution of the method when the previous execution results in an exception.
42

53
You can use the `AutoRetry` aspect to improve the stability of your application by making it more resilient to anticipated, temporary failures.

Framework/PostSharp.Samples.CustomCaching/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.CustomCaching
2-
31
Caching your method's return value makes the method execution faster, trading memory for time by storing the return value in a cache.
42
If you call the method again then you can return a value stored in the cache, instead of doing time consuming calculation
53
all over again.

Framework/PostSharp.Samples.CustomLogging/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.CustomLogging
2-
31
Have you ever had the problem where your program misbehaves and you just do not have a debugger attached
42
at the moment? Or that some bug is appearing occasionally and you just don't know how to reproduce
53
such a case manually? The usual solution here is logging. But introducing logging into your code comes with

Framework/PostSharp.Samples.Encryption/README.md

+1-3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,4 @@
1-
# PostSharp.Samples.Encryption
2-
3-
This example demonstrates how to build aspects that automatically encrypt or decrypt parameter
1+
This example demonstrates how to build aspects that automatically encrypt or decrypt parameter
42
values. The only encryption algorithm implemented in this example is string reversal. This
53
is not real encryption, of course! In practice, you would probably use a format-preserving
64
encryption algorithm from a third party.

Framework/PostSharp.Samples.ExceptionHandling/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.ExceptionHandling
2-
31
Exception handling is one of the most common sources of boilerplate code and makes the business logic less readable. With PostSharp, you can
42
define exception handling policies centrally and apply them to your business logic from a single point.
53

Framework/PostSharp.Samples.MiniProfiler/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.MiniProfiler
2-
31
MiniProfiler from the makers of StackOverflow is one of the most popular and most useful libraries for
42
ASP.NET developers. Thanks to MiniProfiler, you can easily track the execution time of selected methods.
53

Framework/PostSharp.Samples.Persistence/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Persistence
2-
31
This example shows two aspects that cause a field or a property to be backed by a persistent storage:
42

53
* `RegistryValueAttribute` is an aspect that persists a field or property into a Windows registry value.

Framework/PostSharp.Samples.Profiling/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.Profiling
2-
31
This example demonstrates how to build an aspect `ProfileAttribute` that you can apply to any method to measure
42
its execution time.
53

Framework/PostSharp.Samples.SessionState/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.SessionState
2-
31
This example demonstrates how to use `LocationInterceptionAspect` to persist a field or property in the ASP.NET session state or page view state.
42

53
* The `SessionStateAttribute` class is a Aspect that persists a field or property into the session state. This attribute can be

Framework/PostSharp.Samples.Transactions/README.md

-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
1-
# PostSharp.Samples.Transactions
21

32
This example demonstrates how to build an aspect `RequiresTransactionAttribute` that forces the method to which it is applied
43
to execute into a transaction. The aspect relies on the `System.Transactions` namespace, which supports distributed transactions,

Framework/PostSharp.Samples.ValidateResourceString/README.md

-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
# PostSharp.Samples.ValidateResourceString
2-
31
When you want to validate values assigned to method parameters, the validation is most often executed at runtime.
42
You do not get any warning that something is broken until you execute a method that is being validated during testing.
53
If you do not execute the method during testing then you are not notified about a possible bug at all.

0 commit comments

Comments
 (0)