Using the adCenter API with Microsoft Visual Studio 2008 requires that you use the Microsoft .NET Framework version 3.0 or the .NET Framework version 3.5, and then add a service reference to your project.

Create a project that uses the adCenter API in Visual Studio 2008 by using the following steps.

1. Open Visual Studio 2008.
   
2. Create a new Visual C# or Visual Basic project. In the New Project combo box, make sure that .NET Framework 3.0 or .NET Framework 3.5 is selected.
   
3. After the project has been created, select Project, and then select the Add Service Reference command.
   
4. We recommend that you use message contracts when you create your client proxy, although it isn't required. Create a client proxy that uses message contracts by using the following steps:
   
   1. In the Add Service Reference dialog box, click Advanced.
      
   2. In the Service Reference Settings dialog box, select the Always generate message contracts check box as shown in the following figure.
      
      
      Always generate message contracts check box
      
   3. Click the OK button.
      
   For more information about message contracts, see Message Contracts.
   
5. In the Address field, type the URL of the Web service to create a service reference for. For example, to create a service reference for the sandbox reporting Web service, type "https://sandboxapi.adcenter.microsoft.com/Api/Advertiser/V6/Reporting/ReportingService.svc" in the Address field.
   
6. Click Go. Visual Studio then contacts the given URL and downloads the necessary information.
   
7. Type a descriptive name for the namespace in Namespace. This can be any name you want as long as it’s unique within your project; for example, "adCenter_ReportingService".
   
8. Click OK. Visual Studio then creates the necessary files and adds them to your project.
   
9. Repeat these steps for any other service references you may need.
   

To use the Web service, add a using or Imports statement to your code to include the service reference. The following is what a using statement would look like for the reporting service reference that was previously created.

using <project name>.adCenter_ReportingService;

The following is what an Imports statement would look like for the reporting service reference that was previously created.

Imports <project name>.adCenter_ReportingService

Replace <project name> with the name of your project.

If you'll be adding or updating assets, you'll have to update one of the following sets of configuration values.

If your binding point is defined in your app.config file, open it and then change the following items:

• Set the maxArrayLength attribute of the readerQuotas element to "70000".
  
• Set the maxReceivedMessageSize attribute of the basicHttpBinding element to "1500000".
  

If you are manually creating your binding point, change the following items:

• Set the MaxArrayLength property of the BasicHttpBinding.ReaderQuotas property to 70000.
  
• Set the BasicHttpBinding.MaxReceviedMessageSize property to 1500000.
  

Changing these settings allows the SOAP messages to be large enough to handle the maximum asset sizes.

For more information about assets, see Advertising Assets.

You are now ready to begin writing code that uses the adCenter Web services you have added references to.

Using the adCenter API with Microsoft Visual Studio 2005 requires that you complete a process that includes four steps. Each one of the following steps represents a procedure; each is covered in this topic in the order shown:

1. Install the Microsoft.NET Framework version 3.0.
   
2. Create the required client proxy files by using svcutil.exe.
   
3. Add the newly created client proxy files to your project.
   
4. Add the required references to System.Runtime.Serialization.dll and System.ServiceModel.dll.
   

For more information and a step-by-step example of how to create a program that uses the adCenter API, see Hello Microsoft adCenter Sample in C#.

Install the .NET Framework 3.0

Create the Client Proxy Files

svcutil https://sandboxapi.adcenter.microsoft.com/Api/Advertiser/V6/CampaignManagement/CampaignManagementService.svc /config:app.config /messageContract /n:*,adCenter.CampaignManagementService /language:csharp /out:CampaignManagementService.cs

Add the Client Proxy Files

Add the Required References

Using message contracts creates client proxy code that uses the Request and Response sets of classes for the service operations. For example, the AddCampaigns service operation uses an AddCampaignsRequest object, and then returns an AddCampaignsResponse object. The set of Request classes contains all the header and parameter information that is passed to the service operation. The Response set of classes contains all the information that has been returned from the service operation.

If you don’t use message contracts, the signature of the service operations is significantly different. Without message contracts, each service operation uses all the header and parameter information as parameters to the service operation rather than wrapping them in a data class. For example, the signature of the AddCampaigns service operation with message contracts is as follows.

public AddCampaignsResponse AddCampaigns 
(
  AddCampaignsRequest request
);

By comparison, the signature of the CampaignManagementServiceClient.AddCampaigns service operation without message contracts is as follows.

public ApiCallTrackingData AddCampaigns 
(
  ApplicationToken applicationToken,
  System.Nullable<int> customerAccountId,
  DeveloperToken developerToken,
  UserCredentials userCredentials,
  int accountId,
  Campaign[] campaigns,
  out int[] campaignIds
);

For more information about message contracts, see Using Message Contracts.

Concepts