We are about to update our Primavera system from 6.x to 8.2. We have som applications that uses the webservice but having some problems.
In Primavera 6 we used Primaveras version of the DLL helper called: p6WSStubs.dll
In the newer versions they have a guide that explains how to create this file witch we have done.
However the classes and methods in the 2 files are not completely identical.
We uses Visual studio.
In the old Version we Could create an instance of a class called Authetication service like this:
Primavera.Ws.P6.Authentication.AuthenticationService auth = new Primavera.Ws.P6.Authentication.AuthenticationService();
in the new version we have created the Namespace Primavera.Ws.P6.Authentication like descriped in the guide but I only have the Classes and methods shown here:
Does anyone have any experience with the differences in webservice in the 2 version?
You can instantiate the AuthenticationServicePortTypeClient and use it as you used the service. Assuming you might be using C# 4.0 with VS 2010, that uses WCF to connect with SOAP based services and the way you interact is a little different than Microsoft WSE in .net 2.0.
Related
I have a Visual Studio 2015 solution with 2 projects:
A classic ASP web site.
A C# class library.
How do I call the C# methods from within the classic ASP pages?
I will deploy the solution to Azure App Services.
I do know that I could create a web API and call it that way. But I am wondering if there is any other way to do this.
UPDATE:
I made the C# class "COM-Visible" and checked the “Register for COM interop” option, and everything works correctly on my development machine.
But when I publish the solution to Azure Web Services, it doesn't work. The Classic ASP page runs fine, but I get this error when trying to create the object:
Server object error 'ASP 0177 : 800401f3'
Server.CreateObject Failed
/index.asp, line 34
800401f3
It seems “Register for COM interop” doesn’t work in Azure App Services. I know I could create a VM and register the dll manually, but I would prefer to use Azure App Services instead.
I think the two methods you mentioned - Web API (or similar intermediary service) and Server.CreateObject (needs a COM-visible .NET assembly) are your only two options in Classic ASP.
If the .NET assembly/library you want to use is not COM-visible, and you don't have access to source code, you can create a wrapper - your own .NET assembly that is COM-visible, with pass-through methods - you call your assembly from Classic ASP, and your assembly passes required parameters to the library you actually want to use, and returns results of the corresponding methods.
I have a WCF service which is used by two client applications, one is a web application and the other is a Windows forms application.
When I add a service reference to the web application it works perfectly.
But, when I add a service reference to the Windows application it doesn't generate the proxy class.
Then I run selected the "Reuse types in referenced assemblies" in configure service reference section and it generates the reference with XML serialization. That is not what I needed because it gives me lot of errors since I'm using GUID everywhere.
Can anyone explain me how to generate the proxy class with runtime serialization? (both client application use same version of visual studio - Vs2010)
I'm really struggling with this and your help is highly appreciated.
You can use svcutil to generate proxy class. Add these proxy class in a DLL and then reference it in your Web and Windows application. In this way, you don't need to rely on Visual Studio and will have consistent proxy code for both Web and Windows app
More details - http://msdn.microsoft.com/en-us/library/aa702581(v=vs.110).aspx
I need to consume an existing web service in ASP.net.
The documentation of the website that provides the web servicesays that I have to use WSDL.exe to generate a stub, but I can't find this tool.
I also tried the Add web reference wizard in Visual Studio 2010 (VS2010), but if I paste the URL in, VS2010 doesn't work anymore.
What am I missing?
As far as I remember there should be a choice between .net 2.0 and WCF services.
Try to select .net 2.0 web service type. We had to do it for using SOAP web services running on Python.
You might also try using the Add Service Reference Wizard instead - worked for me for WebServices the Web Reference Wizard did not like quite as much. Make sure to use the link to either the asmx (if it's one) or the .wsdl
As far as I know, you can't create SOAP webservice with .net 4. When you creating new project, you need to choos .net 3.5 or earlier first, and then create project.
As for creating stub from existing wsdl, I don't know how to do it.
Situation: I am trying to consume a clients web service for CC authorization. They are not publishing the WSDL file on there site, but they have provided the WSDL file. I am using Visual Studio 2005 and creating a web application that consumes the web service.
The only reference to this error that seems to apply is here: http://followtheheard.blogspot.com/2007/12/consuming-web-services.html. I installed WSE3.0 and configured my project to use WSE and am calling the WSE version of the web reference and I am still getting this error. Any help would be appreciated.
Apparently there is poor interoperability between web services written in Java requiring WSE and Visual Studio 2005. Upgrading to Visual Studio 2008 allows for easier use of the WSE3.0 toolset.
I have a WSDL file defining the interface for a web service and I want to implement that service (i.e. producer/server code) using C#, ASP.Net and Visual Studio 2005. Setting up a Web Reference as consumer of a web service is a breeze, but as a producer isn't as obvious.
In the java world there is wsdltojava. Is there something similar to this?
Yes there is. And wait for it, it is called wsdl.exe!
The file lives in the Microsoft Windows SDK bin directory (for older version of .NET, the .NET SDK may be in another location).