Have you needed to fax from either ASP.Net or XML Web Services?
If so, we have the solution for you! We too have felt the pain of needing fax services from ASP.Net and XML Web Services and now we can offer you the solution you have been looking for.
With WillowTree Fax Proxy and Fax Client you can quickly and easily add fax sending capability to your .Net web applications. Using C# we have built a Windows Server Service for proxying your Fax requests from any .Net application (even non ASP.Net apps) using our easy-to-implement C# client. We even offer a full source package in case you need to make changes to the code so it can do other tasks you require.
At WillowTree Software, solutions are our business. Let us know if there is a solution you need and we will work with you to provide a stable, scalable, and easy to implement solution…
Download a 30 day trial: http://shop.willowtreesoftware.com/Default.aspx?tabid=242
WillowTree Fax Service Documentation
WillowTree Software, Inc.
http://www.willowtreesoftware.com
Overview
There are 4 parts to the WillowTree Fax solution:
1. WillowTree Fax Client -- The WillowTree Fax Client is a 100% .Net assembly for use with the WillowTree Fax Service. The client can be used to send faxes from an ASP.Net page, a Windows Forms application, or any other .Net application. It is compatible with any .Net language, including VB.Net, C#, J#, and Managed C++.
2. WillowTree Fax Service -- The WillowTree Fax Service is a Windows Service that accepts fax requests from the Client and forwards them to the Microsoft Fax server.
3. Microsoft Fax Service -- This service actually sends the faxes. The WillowTree Fax Service is designed to be a simple, yet flexible front end for the Microsoft Fax Service.
4. WillowTree Dead Fax Handler Service -- This service can be used separately or in conjunction with the other WillowTree Fax products. It enables developers to monitor the Microsoft Fax Service and provide custom processing for faxes that have failed. The WillowTree Dead Fax Handler provides a simple Plugin architecture that allows developers to write their own handlers. For instance, when a fax job fails, an email could be automatically sent or a database entry made.
Why should I use the WillowTree Fax solution, rather than using Microsoft's API directly?
1. Easily send faxes from ASP.Net -- Because of security restrictions and COM Interop issues, it can be very difficult to use the Microsoft Fax Service Client API directly from an ASP.Net page. The WillowTree Fax Client is a 100% .Net assembly (no COM Interop involved) that can be used to send a fax from a web application with just a few lines of code.
2. Asynchronous faxing -- The WillowTree Fax Client does not block while the fax is being sent (which can take several seconds to more than a minute). This allows web pages to return quickly, rather than causing the user to experience a lengthy wait. If a fax should fail, it can be automatically handled later by the WillowTree Dead Fax Handler Service (see below).
3. Enhanced built-in error logging -- The WillowTree Fax Service allows developers to easily configure .Net TraceListeners to capture any errors returned from Microsoft's Fax Service.
4. Monitor failed faxes with the WillowTree Dead Fax Handler Service -- This service allows developers to write their own plugins to process faxes that failed to send (for instance, if the service tried several times but the phone line was always busy). Create plugins to send emails, write database entries, or even try resending the fax.