Home/ Questions/Q 8378813
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T16:01:01+00:00

I have a WP7 project, which will invoke a REST web service in Azure

  • 0

I have a WP7 project, which will invoke a REST web service in Azure (MVC4 WebApi).

My WP7 project has models that it serializes to JSON and then sends to the web service.

The web service deserializes the data sent from WP7 and instantiates the models again before saving them to Azure Table Storage.

How can I share the Model classes between the projects? Right now I’m just copying the cs files over, and I have to update both sets if I make a change to the models. I was hoping a simple class library project would be able to be referenced from both projects, but WP7 couldn’t handle that.

What should I do?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There are many solutions for this issue:

    • You could use a T4 template to read the entity and generate a class your WP7 project that only contains the properties of the object without reference to the Table Storage specifics (like TableStorageEntity): http://weblogs.asp.net/cibrax/archive/2009/03/11/code-generation-with-t4-an-entities-to-dto-example.aspx

    • You could split your entity over 2 files, one with the TableStorage specifics like TableStorageEntity and one file containing only the properties of the entity (use partial classes for this). Then you can add the file containing only the properties in your WP7 project as a link.

    • Create a DTO (or whatever you call it) class manually and use something like AutoMapper to map between the DTO and the TableStorage entity. Store the DTO in a portable library so it can be used by every kind of project. In my opinion this is the best solution since you don’t want to completely expose your entities to “the outside world”. An example would be a list of users. You wouldn’t want to return all fields including password, hash… and other sensitive info. It would be better to have a separate class that only contains the info you want to expose externally.

    • 0