Hi,
In this series of blog posts we will help you to design, develop and debug the Resource DLL you are developing to give your application high-availability with Windows Server 2008 & 2008 R2 Failover Clustering.
We recommend you start with the other blog post in the series:
· Part 1: http://blogs.msdn.com/b/clustering/archive/2010/03/11/9976620.aspx
· Part 2: http://blogs.msdn.com/b/clustering/archive/2010/03/30/9987135.aspx
· Part 3: http://blogs.msdn.com/b/clustering/archive/2010/04/21/9999736.aspx
· Part 4: http://blogs.msdn.com/b/clustering/archive/2010/08/18/10051655.aspx
In this post we will describe how to write to logs from within the Resource DLL.
First familiarize yourself with the Startup call: http://msdn.microsoft.com/en-us/library/aa372931(VS.85).aspx.
During the Startup call you are being provided with the LogEvent function pointer. This is designed for the diagnostics logging, and the messages you log using this method go straight to the cluster log and are interleaved with messages from the other cluster components. You can create or see the log by following the instructions provided in this blog post: http://blogs.msdn.com/b/clustering/archive/2008/09/24/8962934.aspx.
For more information on the logging see http://msdn.microsoft.com/en-us/library/aa370823(VS.85).aspx. Many of the Cluster Administrators are familiar with the cluster log so writing your message there is the best way to go about providing information to users.
I hope this series of blog posts will be helpful when you design your own Resource DLL.
Thanks,
Vladimir Petter
Senior Software Development Engineer
Clustering & High-Availability
Microsoft