Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 520691
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T08:10:18+00:00 2026-05-13T08:10:18+00:00

I’m trying to learn to call SharePoint Web Services from an external C# client.

  • 0

I’m trying to learn to call SharePoint Web Services from an external C# client. I’m using MOSS 2007 and VS 2008. There are lots of examples on the web of doing so, but most of them seem to be using a different form of each of the Web Service APIs than what I’m seeing in Visual Studio. My question is…what up wit dat?

When, for example, I launch Visual Studio 2008, create a new C# Console Application project, and then do a "Add Service Reference…" to add a reference to "http://myspserver/_vti_bin/Lists.asmx", the resulting namespace (with whatever name I chose to give it) contains the classes ListsSoap, ListsSoapChannel, and ListsSoapClient but no Lists class.

But many of the examples I see expect there to be a Lists class in that namespace. I keep seeing code like this:

sharepoint.lists.Lists l = new sharepoint.lists.Lists();
System.Net.NetworkCredential cred = new System.Net.NetworkCredential("your username here", "your password here");
l.Credentials = cred;
XmlNode n = l.GetListItems("your calendar name here", null, null, null, null, null, null);

This code doesn’t compile for me. I wouldn’t expect it to as browsing the binding to the Lists service ("sharepoint.lists" in this case) shows me these other classes I mention above but no Lists class.

And it doesn’t work to replace the use of Lists() with one of the other classes, like ListsClient(). If I do that, I have problems later on. For example, the ListsClient object has no "Credentials" property, but rather a "ClientCredentials" property.

It’s almost as if I’m using an older or newer form of the APIs, but I’m using MOSS 2007 (WSS 3.0) and the examples I’m seeing say they’re written against the same SP versions.

What am I missing or doing wrong here? Where does this Lists class come from?

Humble TIA for any help.

PS: The code above comes from here: Link

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T08:10:19+00:00Added an answer on May 13, 2026 at 8:10 am

    “Add Service Reference” uses WCF, and what you see are the expected results of compiling the WSDL. Read up more on Windows Communication Foundation to find out how to use those classes.

    If you want to generate a Lists class (more common as you’ve found out), use the “Add Web Reference” dialogs instead – these use the System.Web.Services classes, not WCF.

    -Oisin

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 377k
  • Answers 377k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer The IP length field was consequently counting 8 bits too… May 14, 2026 at 8:46 pm
  • Editorial Team
    Editorial Team added an answer std::vector<T>::pointer is not std::vector<T>*, it is T*. Don't worry about… May 14, 2026 at 8:46 pm
  • Editorial Team
    Editorial Team added an answer "Cursor" is used to refer to the mouse cursor which… May 14, 2026 at 8:46 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.