Hi Steven,
Thanks for the reply, I've had a read over those examples but they don't quite describe what I'm trying to achieve. I'll add some pseudo code below to illustrate the problem a little better:
Say I have a windows store class library:
// class library
public sealed class User
{
public string Name { get; set; }
}
public IList<User> GetUsers()
{
return new List { //users in here };
}
And I have a runtime component:
// runtime component
public sealed class RTClass
{
public IList<User> GetUsersFromClassLib()
{
var classLib = new classLib();
return classLib.GetUsers();
}
}
In this situation, my 'User' class is reported as a non valid runtime type (even though there isn't anything which, if placed inside the runtime component wouldn't be valid), presumably because it's not defined inside the runtime components namespace.
To put the example into context, my class library is a BL/Service library which will access entities from a database and what I'd like to be able to do is map between these db entities to 'viewmodel' RT types. My original hope was to user a constructor in
my RT component which would take the db entity as a parameter. e.g.
// runtime component
public sealed class RTUser
{
public RTUser(DBUser user)
{
//do mapping in here, e.g.
return new RTUser
{
FullName = user.FirstName + " " + user.LastName;
}
}
}
I can't seem to make this work as the RT component doesn't like the fact that my DBUser isn't a valid RT type (I can't adjust the DBUser class, which isn't sealed, so I don't have a lot of options here.)
So, my second thought was to create a DTO type library which would be able to perform the mapping between DBUser and RTUser and return instances of RTUser to the RTcomponent. Unfortunately the RT component still doesn't want to return types defined in another
class library, even if they are marked as sealed and don't return anything which would be fine if defined in the RT component directly.
You could say 'just define the RTUser type in the RTcomponent and do the mapping in there'..which I am currently doing, but because I can't user the DBUser as a parameter for any mapping function I'm having to create lengthy, non re-usable functions in my
RTcomponent, which look something like this:
// runtime component, real example when getting surveys
// what I have to write:
public IList<SurveyViewModel> GetSurveys()
{
var data = _surveyService
.GetSurveys()
.Select(x =>
new SurveyViewModel
{
Id = x.Id,
SurveyDate = x.Date,
SurveyTitle = x.Title,
SurveyType = x.SurveyType.Name,
Locked = x.Locked,
SeverityColour = this.GetMaxSeverity(x.SurveyCompartments),
CompletionPercentage = this.GetCompletionPercentage(x.SurveyCompartments),
Compartments = x.SurveyCompartments.Select(z => new CompartmentViewModel
{
Name = z.Compartment.Name
}).ToList(),
Group = new Group
{
key = "Survey",
title = "Surveys",
subtitle = "Surveys"
}
});
return data.ToList();
}
// what I'd like to write:
public IList<SurveyViewModel> GetSurveys()
{
var data = _surveyService
.GetSurveys()
.Select(x => new SurveyViewModel(x))
return data.ToList();
}
Does anyone have any thoughts on how best to get around this? I'm open to any ideas!
Many thanks,
Doug
