Frustrating Lack of support with Sproxy.exe

  • Thread starter Thread starter Rob Schieber
  • Start date Start date
R

Rob Schieber

I am pretty frustrated with Microsoft and their lack of support with the
Sproxy.exe tool included with VS.Net.

Im using VS.Net EA and I wanted to create a C++ webreference to the
Amazon.com web service:
http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl

Now Sproxy.exe blows errors left and right when you try to add this. It
seems that Sproxy doesn't now how to interpret attributes, lists,
annotations etc... This seems to have been a known issue by microsoft
for going on 3 years now and they still havent fixed it. So either they
just plain havent fixed sproxy.exe, or they have and aren't going to
distribute the updated version to VS 2002 users. Either way, I think
the lack of support stinks.

P.S. Since MS doesn't seem to care too much about Sproxy, how are VC++
users supposed to consume web services, seeing as how they are retiring
the soap toolkit? Am I missing something here?
 
Hi Rob!
I am pretty frustrated with Microsoft and their lack of support with the
Sproxy.exe tool included with VS.Net.
Click to expand...

I do not know sproxy... so I cannot help you with that problem... sorry.

P.S. Since MS doesn't seem to care too much about Sproxy, how are VC++
users supposed to consume web services, seeing as how they are retiring
the soap toolkit? Am I missing something here?
Click to expand...

It seems that MS will not improve the C++ SOAP-Toolkit... this is very
bad for all (native) C++ developers; I agree completely!
See:
http://msdn.microsoft.com/webservices/webservices/building/soaptk/default.aspx

You also can use other SOAP C++ implementations. For example:
http://gsoap2.sourceforge.net/


The recommeded way from MS is to use managed C++ and then use the
..NET-Framework Web-Services.

--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/
 
Just to affirm Tomas's point, the Debug version initializes most variables
to zero. The Release version will not initialize anything 'naturally'
(meaning without you writing code to do so), and hence many of the variable
are often given a 'random' value upon loading ('random' in that they keep
the contents of the memory addresses they happen to get assigned to).

Thus, your new errors are likely the result of some variable that works fine
if initialized to zero, but don't work if not initialized to zero (or not in
some range, non-negative, etc.). Since an application doesn't always get
loaded at the same place and memory, and because even the same place in
memory can have different values depending on when you load your program
(that's why it's RAM not ROM...hehe), you can get random bugs and un-stable
executions of the Release version (i.e., it might do different things on
different runs depending on the 'random' nature of your variables) even if
it is totally stable in Debug mode.

Hope that helps!!! : )
 
Back
Top