Files
mono/mcs/class/System.Web/Test/tools/README
T
Marek Habersack 73c3bfba56 2010-02-03 Marek Habersack <[email protected]>
* AssemblyInfo.cs: added back InternalsVisibleTo for the test
        assembly - it's needed to access CacheItemPriorityQueue

2010-02-03  Marek Habersack  <[email protected]>

        * OutputCache.cs: DefaultProviderName checks if there was any
        provider configured and, if not, returns a built-in provider's
        name.

        * SqlCacheDependencyAdmin.cs: added

        * OutputCacheProviderCollection.cs: added

        * OutputCacheProvider.cs: added

        * OutputCacheModule.cs: uses the 4.0 extensible output cache
        provider model now (also internally in the 2.0 profile)
        OutputCacheProvider is retrieved on every request using
        HttpApplication.GetOutputCacheProviderName (4.0+). In the 2.0
        profile an instance of InMemoryOutputCacheProvider is always
        returned.

        * InMemoryOutputCacheProvider.cs: default output cache provider
        for ASP.NET 4.0, also used internally in the  2.0 profile.

        * CachedVaryBy.cs: made the generated key shorter

        * CacheItemPriorityQueueDebug.cs: debugging support for
        CacheItemPriorityQueue. Most of the code is compiled only when the
        DEBUG macro is defined. Debugging support includes recording of
        the queue operations sequence which is output to an XML file on
        appdomain shutdown. The recorded sequence files can be used to
        generate NUnit test cases for the priority queue (see
        ../Test/tools/README)

        * CacheItemPriorityQueue.cs: rewritten using an array based heap
        instead of a binary tree based one - implementation is simpler,
        faster and more elegant. Heap is initially 32 entries long and
        its size is doubled every time it fills up. After reaching a
        threshold (8192 entries currently) it is shrunk to the number of
        items + 1/3 of item count in order to preserve memory.

        * CacheItem.cs: added a Guid field to easier distinguish items
        (mostly for debugging purposes)

        * CacheDependency.cs: minor performance improvements

        * Cache.cs: better handling of timer periods

2010-02-03  Marek Habersack  <[email protected]>

        * HttpApplication.cs: GetOutputCacheProviderName returns the value
        of OutputCache.DefaultProviderName

        * HttpRuntime.cs: internal cache is used to hold the dependencies
        now.

2010-02-03  Marek Habersack  <[email protected]>

        * CacheItemPriorityQueueTest_generated.cs: added

        * CacheItemPriorityQueueTest.cs: added

2010-02-04  Marek Habersack  <[email protected]>

        * Helpers.cs: added a helper method for checking of HTML mentions
        any .NET exceptions.

2010-02-03  Marek Habersack  <[email protected]>

        * Makefile: added targets to compile cache priority queue tests
        generator and to generate the tests themselves

svn path=/trunk/mcs/; revision=150855
2010-02-04 13:53:55 +00:00

35 lines
1.4 KiB
Plaintext

Tools
-------
* HtmlWriter.cs: it provides a custom HtmlTextWriter implementation with
logging capabilities to help figuring out which method in HtmlTextWriter
you should invoke and where to do it.
How to use it.
---------------
* Run 'make'. It will generate HtmlWriter.dll.
* Copy HtmlWriter.dll to the 'bin' directory.
* Copy web.config to the directory in which you run xsp
(the parent of 'bin').
* There are 2 environment variables used:
-HTMLWRITER_FULLTRACE=yes: displays the stack trace for
every method called.
-HTMLWRITER_FILE=[yourfilename]: output goes to a file
instead of stdout.
The default output is a sequence number, the function called and its
arguments.
* cache-pq-test-generator: a utility to generate NUnit tests for System.Web.Caching
CacheItem priority queue, used to store timed cache items. The utility generates
code from sequence files (found in CachePQTestGenerator/Sequences/*.seq) which, in turn
are generated by the CacheItemPriorityQueue class itself if System.Web is compiled with
the DEBUG macro defined. To generate the sequence files just run your application as usual
and at the exit a .seq file will be created in the application's root directory.
Copy the generated .seq file to the sequences directory mentioned above and run:
make generate-cache-pq-tests
which will generate the ../System.Web.Caching/CacheItemPriorityQueueTest_generated.cs file