Home/ Questions/Q 3783386
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T11:13:01+00:00

I’m running two instances of VS2010 on my local machine. One instance is running

  • 0

I’m running two instances of VS2010 on my local machine. One instance is running my Web Service (written in C#). The other instance is running my MVC web app (also C#). The MVC web app has a reference to the web service. I can successfully invoke web service methods from within the MVC app.

In my web service is a PageNavigation class:

// PageNavigation.cs
using System;
using System.Collections.Generic;
using System.Text;

public class PageNavigation
{
    public string Page_Number { get; set; }
    public string Page_Count { get; set; }

    public PageNavigation()
    {
        Page_Number = "1";
        Page_Count = "2";
    }
}

By default, this should return an object with auto-implemented properties when I call the class constructor:

WebService.PageNavigation pageNavigation = new WebService.PageNavigation();

This works when constructing a PageNavigation object elsewhere in the web service. 

pageNavigation.Page_Number
"1"
pageNavigation.Page_Count
"2"

However, running the same line of code on the MVC isn’t giving the same result; the object’s properties are all null values. 

pageNavigation.Page_Number
null
pageNavigation.Page_Count
null

Is this the expected behavior? Is there a way to populate the properties with default values as intended? If more information is needed please let me know and I will update the question.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The service reference only sees the schema of your object, not business logic; in your case, your service reference just created a shell data type in the MVC application. When you create a service reference, it’s actually creating another type with the same property names and types as the type defined in the service.

    For your particular scenario (simply providing default property values and not more general business logic), you should be able to apply the [System.ComponentModel.DefaultValue] attribute to your properties in order for the class generator to recognize that these properties should be populated with a default value.

    Incidentally, if the service reference were reusing existing types (if you had this type in a common library that was referenced both by the service and the application, for example), then your business logic would be intact.

    An alternative would be to implement a factory pattern, whereby you call a function on the web service that instantiates (and optionally populates) the data object, then returns it to the client.

    • 0