I am working on an old project, not currently used, that I pulled from our source backups. I have experience as a Sharepoint user but this is the first time I have been developing for or installing/deploying it.
There is no documentation for this project, at all (infurating), and I am having great trouble working out where some of these files are supposed to be installed on my Sharepoint (WSS3) server.
Research showed me you need:
.disco file (for automatic discovery) .WSDL file (dynamic endpoint required to map virutal directory to service) .ASMX file (the ASP webservice)
This guide explained that you should deploy to
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI however it mentioned placing
wswsdl.aspx into ISAPI.
It doesn't mention where these files are supposed to come from? Should I be renaming the generated WSDL and DISCO files?
I did also read how these files are generated. Register service assembly in GAC & generate with Disco.exe.
(I tried to do this myself for a test msdn guide but it errored out generating the files with
HTML document does not contain Web service. Apparently I shouldn't need to create any more files to deploy this solution though.)
The files I have are... (some ommisions)
-- SharepointWebService (website project) -- -root- Service1.asmx Service.asmx.cs SharepointWebService.csproj //...etc > Web References >>UserProfileSharepointService >>> -ContactData.datasource >>> -GetUserProfileByIndexResult.datasource >>> -Reference.cs >>> -Reference.map >>> -userprofileservice.disco >>> -userprofileservice.wsdl >>> -vssver.scc >>WebsSharepointService >>> -CustomizedPageStatus.datasource >>> -Reference.cs >>> -Reference.map >>> -vssver.scc >>> -webs.disco >>> -Webs.wsdl
One thing that confuses me about this is that the SharepointWebservice appears to be referecing two other webservices. I was able to find out where they are supposed to be, the virtual directory anyway, by examining the properties.
However the program which utilises the webservice calls on Service1.asmx, which has no WSDL or DISCO files in the solution. I would really really like to know if I have to generate some for this myself, as in they are missing, or if the person who designed this intended something else.
Unfamiliar with this subject so I'd really appreicate some pointers, so I can understand how this is supposed to work. Any small alleviation of my confusion appreciated, thanks!