Hi Andy,
Regarding on sending FAX, the raw interface on windows platform should be
tha TAPI api, however, due to the complexity of TAPI and time consuming for
completely developing a FAX solution via TAPI, it does be preferred to use
an existing component. Here are some FAX components I've searched:
#FaxMan - ActiveX/DLL/.NET - V4.0
http://www.componentsource.com/produ...man/index.html
#RFax 1.1 for .NET - Fax component
http://www.java4less.com/fax_dotnet.htm
IMO, since your main application is ASP.NET web application, you can
consider separate the FAX sending service from your web application. for
example, you can use a standard winform or console or service application
to host the FAX sending program and let your web application send FAX
sending request to the FAX service application (through remote method call)
in a queued model, this can make your web application loose coupled with
the FAX functionality.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.