ATL Server Library and Tools

CREATED ISSUE: Missing CHttpServer

thomasmxrd — Tue, 06 May 2008 02:44:23 GMT

Microsoft eliminated the MFC ISAPI class CHttpServer and related headers/libs from Visual Studio 2008.

Pages like this one seem to imply they can be found in your project: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2470867&SiteID=1&pageid=0

However, I don't see CHttpServer in the AtlServer project anywhere? Can someone elaborate on this issue? Where can we get CHttpServer support in VS 2008, and why was it removed without warning by Microsoft?

NEW POST: Is ATL Server still alive?

Ranja — Tue, 01 Apr 2008 06:27:17 GMT

The ATL Server source files have not been updated for a year.
I doubt this project is still working.
Should I start to think rewriting the vast amounts of source codes I've written to make use of ASP.NET technology?

CREATED ISSUE: CMimeHeader::SetSenderName() doesn't Q encode non US-ASCII

b3nt_pin — Thu, 13 Mar 2008 19:11:46 GMT

While CMimeHeader::SetSenderName() converts from Unicode, it does not perform the appropriate encoding for non US-ASCII characters.

NEW POST: SOAP 1.2 Support?

ruili — Fri, 07 Mar 2008 20:31:54 GMT

Does the current release support SOAP 1.2?

NEW POST: ATL SOAP Server in VS2008?

Plurilogic — Tue, 04 Mar 2008 21:32:46 GMT

I hope also that a solution for "ATL Server attributes" for VS2008 will be found by someone in a near future (Microsoft ?) ! The /FX option produce unreadable code !

We have a very large project (over 2000 sources files.) with more than 30 web service functions and very complex data structure being used by these functions.

So, in the mean time, we isolated attributes reference in only two files (a .cpp an a .h) These two files are compiled with the /FX option with VS 2005, and the mrg files produces are used instead in our VS2008 project.

Since the definition of web services does not change often, we will not have to recompile with VS2005 too often.

NEW POST: Errors with Exchange WSDL

mcanti — Mon, 25 Feb 2008 19:52:35 GMT

Hello,

I want to generate proxy class for Exchange Server 2007 SP1 web services. The error I get from sproxy.exe is:

SDL1029: no web service methods to generate

If I add the web service method to the downloaded Services.wsdl file, I receive another error:

SDL1000: Unknown error

I have tried to debug sproxy.exe but I don't think I will find the cause very soon :-)
Could someone help me? I can send the Services.wsdl file, the messages.xsd and the types.xsd files for Exchange Server.

Thank you.

NEW POST: ATL SOAP Server in VS2008?

pbarnes — Wed, 20 Feb 2008 15:49:45 GMT

jpsanders,
Thanks for your reply. Unfortunately, this is the "solution" I already found as indicated in my original post. I can get it to build in VS2008, that was not the problem. The problem is that this solution is not workable.

When you replace the attributes with the code that they inject, you get lots of unmaintainable machine generated spaghetti code defining the SOAP map, data types, the interface, etc (over 13,000 lines in my case.) Look at this generated code for a non-trivial web service and imagine trying to add new SOAP data types (e.g., structs and enums) and/or methods to your interface, or modifying an existing data type or method. Imagine trying to write a brand new SOAP web service in C++ with ATLServer. It's theoretically possible, but certainly not practical.

Also, sure, I could use managed code with or without interop to access a webservice. But I am talking about implementing a web service, not accessing one. Sure, I could expend valuable time and effort rewriting the entire web service in managed code, but that is not my first choice either.

My conclusion is that VS2008+ATLServer no longer support native C++ web services and I will not be upgrading to VS2008 at this time. Perhaps someone will add some kind of support for this to ATLServer in the future. But it is unfortunate that MS did not do anything to preserve backward compatibility in this area.

NEW POST: ATL SOAP Server in VS2008?

jpsanders — Wed, 20 Feb 2008 13:04:59 GMT

I was able to build a couple of ATLServer projects successfully. It was a little painful but ultimately I succeeded. I blogged my experiences here:
(http://blogs.msdn.com/jpsanders/archive/2008/01/17/building-with-atlserver-based-soap-project-with-visual-studio-2008.aspx)

Alternatively, use the Managed classes and wizards in Visual Studio 2008 to access Web Services. You may use COM Interop to use this managed code inside your unmanaged C++ code. COM Interop is discussed here: http://msdn2.microsoft.com/en-us/library/zsfww439.aspx

NEW POST: ATL SOAP Server in VS2008?

pbarnes — Wed, 13 Feb 2008 14:58:19 GMT

I have a SOAP Service with nearly 100 SOAP methods, implemented with ATL Server in VS2005. In trying to port this to VS2008, which does not support attributes, I found the discussion on this site at http://www.codeplex.com/AtlServer/Thread/View.aspx?ThreadId=12010. After following the instructions there to use the /Fx switch to inject the code that the attributes would inject, I end up with nearly 13,000 lines of injected, unmaintainable spaghetti code.

Surely this is not the way to write SOAP Services with ATL Server in VS2008. Surely there are some convenient macros that replace the soap_handler and soap_method attributes of VS2003/2005; something like DECLARE_SOAP_METHOD(...) that allow writing SOAP Services without attributes. Right?? The documentation at http://msdn2.microsoft.com/en-us/library/d73hf29a(VS.80).aspx does not mention any such macros. Where is ATL Server documentation now that it is not part of VS2008?

CREATED ISSUE: CNTLMAuthObject constructor does not initialize m_bProxy

InvaderZim — Tue, 29 Jan 2008 16:42:32 GMT

In <atlhttp.inl>, there are two constructors for CNTLMAuthObject. The default constructor sets m_bProxy to false, but the constructor that accepts a (possibly NULL) IAuthInfo interface pointer does not initialize m_bProxy. It's set in Authenticate(), but seeing this as `true` until that time is confusing.

/////////////////////////////////////////////////////////////////////////////////
//
// CNTLMAuthObject
// NTLM Security Authorization functions
//
/////////////////////////////////////////////////////////////////////////////////
inline CNTLMAuthObject::CNTLMAuthObject() throw() :
m_pSocket(NULL),
m_nMaxTokenSize(0),
m_pAuthInfo(NULL),
m_bProxy(false)
{
SecInvalidateHandle(&m_hCredentials)
}

inline CNTLMAuthObject::CNTLMAuthObject(IAuthInfo *pAuthInfo) throw() :
m_pSocket(NULL),
m_nMaxTokenSize(0),
m_pAuthInfo(pAuthInfo) // <<---- needs ,m_bProxy(false)
{
SecInvalidateHandle(&m_hCredentials)
}

NEW POST: What is settings_file?

alexeys — Tue, 22 Jan 2008 13:09:16 GMT

I've builded VCDeploy and tried to run it. In should be ran in the command line:
VCDeploy.exe options settings_file.

What is "settings_file". I guess this is some XML file.
Where can I find it or its template?

Patch Uploaded

Schmoo — Fri, 07 Dec 2007 15:09:47 GMT

Schmoo has uploaded a patch.

Description:
Added HTTPS Support to wininet soap calls (this is the version with the while loop and not the goto. I am not sure it makes the code cleaner mind, but goto tends to offend).

Patch Declined

Schmoo — Fri, 07 Dec 2007 15:08:27 GMT

Schmoo has declined patch #523.

Comment:
Changed goto to while loop

NEW POST: afxisapi.h not in VC9

FritoBandito — Thu, 06 Dec 2007 00:45:52 GMT

My ISAPI thing is part of a larger system. Surprisingly enough, one of the largest (and simplest) changes in the port was brought about by atlcom.h adding const to the return value of GetPropertyMap(). Go figure.

I haven't gotten around to IIS 7 yet.

NEW POST: afxisapi.h not in VC9

jpsanders — Wed, 05 Dec 2007 14:51:04 GMT

I hear ya 'Frito'

I want through the same detective work. I have tried to simply bring those files over into VS 2008 and build and have not had much success yet (still messing with it in my "spare" time). Of course a real simple solution would be to keep the VS 2005 compiler and linker around for that legacy code and do new development with the ISAPI API's. I have been playing with IIS 7. Developing for IIS 7 is pretty amazing with the integrated pipeline! It would be nice if I never had to play with ISAPI's again and could just use IIS 7 ;-)

NEW POST: afxisapi.h not in VC9

FritoBandito — Wed, 05 Dec 2007 12:54:51 GMT

OK, thanks. It's off to the Platform SDK then.

I was hoping for easy with these that came with the Dev Studios:
C:\Program Files\Microsoft SDKs\Windows\v5.0
C:\Program Files\Microsoft SDKs\Windows\v6.0A

afxisapi.h was in VS 2005 (and earlier) and then removed from VS 2008, why? I've got a working combination filter & extension and porting to VS 2008 has become a detective game. CSI:Dev Studio it is.

CREATED ISSUE: ATLMIME.H - GetRecipientsString()

deruss — Wed, 05 Dec 2007 00:29:22 GMT

Version: ATL Server Source and Headers 9.0.70425 Alpha

Problem:
New code added to used function AtlMimeMakeRecipientsString() means that GetRecipientsString() will always return FALSE.
The problem is that the 'dwLen' parameter will always be zero, and buffer length validation in AtlMimeMakeRecipientsString() will fail the call.

Fix:
In GetRecipientsString() the three instances of this line:
dwLen = *pdwLen - dwTotalLen;
should be changed to this:
dwLen = dwMaxLen - dwTotalLen;
This will correctly maintain the remaining buffer length in dwLen.

NEW POST: AtlServer on IIS 7.0

jpsanders — Tue, 04 Dec 2007 14:50:05 GMT

mattdavison wrote:
Does anyone know the steps to get Visual Studio 2005 debugging to work via F5 on Vista? I have been pulling my hair out with no luck... Thanks to anyone that can help...

Not sure exactly what you are asking here. If you are debugging an ISAPI then the same steps you would use in other OSes applies. If this is a general Debugging question, you would be better served asking this on the MSDN newsgroups (or opening a support case with Microsoft).

NEW POST: afxisapi.h not in VC9

jpsanders — Tue, 04 Dec 2007 14:43:16 GMT

No CHttpServer is not part of AtlServer. This class is a simple Wrapper around ISAPI Extension Development. Then concept of Context and the functions exposed are all thin wrappers around the Win32 API's. You can simply code directly as an ISAPI Extension. The platform SDK and MSDN have serveral samples of ISAPI extensions. If you install the Platform SDK in it's default location you will find a bunch of ISAPI Extension examples in: C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Samples\Web\iis\extensions

Patch Uploaded

Schmoo — Tue, 04 Dec 2007 11:56:40 GMT

Schmoo has uploaded a patch.

Description:
Added HTTPS support for SOAP calls.