Re: link problem in a C++ web service client

Read this and let us know if you have further questions

[1] http://support.microsoft.com/kb/814472/en-us


"Mike Woinoski" <michaelw@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:jJrNe.7286$ZG2.1182451@xxxxxxxxxxxxxxxxxxxxx
> (I'm new to VS, so please forgive me if this is a faq.) I'm writing some
> Java web services and need to test them with C++ clients. I can use either
> a Windows Form application or an MFC application. I used VS.NET 2003 to
> create a C# client that successfully processes SOAP messages to and from
> the Java service. However, I'm having problems with the C++ client.
>
> I created a new solution and a new project with File > New > Visual C++
> Projects
> > Windows Forms Application. Under the project's References, I created a
> > web
> reference to the service WSDL and named the reference donow11service,
> exactly as I did with the C# client. VS gave the following warning when
> creating the proxy:
>
> Creating web service proxy file for donow11service ...
> Writing file 'donow11service.h'.
> donow11service.h
> LINK : warning LNK4243: DLL containing objects compiled with /clr is not
> linked with /NOENTRY; image may not run correctly
>
> I added the following code in the submitButton_Click method:
>
> donow11service::RainOrderService * proxy =
> new donow11service::RainOrderService();
>
> When I build the project, I get the following messages:
>
> Linking...
> stdafx.obj : warning LNK4227: metadata operation warning (00131189) :
> Inconsistent parameter information in duplicated methods (methods:
> orderRecording; type: __boxed_System_Boolean): (0x08000008).
> stdafx.obj : error LNK2022: metadata operation failed (80131195) :
> Custom
> attributes are not consistent: (0x0c000007).
> LINK : fatal error LNK1255: link failed because of metadata errors
>
> If I comment out the line that creates the proxy, the application runs.
> Why are there errors in stdafx.obj? Is there a linker option I need to set
> somewhere? Any help would be much appreciated.
>
> Thanks,
> Mike


.

Loading