Continuing the discussion from NativeTypes namespacing question:
I wanted to bring this up again as a kind of ugly issue. I’ve been dealing with this by naming my service DTOs like
namespace Web.Service.Authentication
{
public class WSAUser : IReturn<WSAUserResponse>
{
}
public class WSAUserResponse
{
}
}
But this just looks bad - and I’m back to square one if I add a new namespace “Web.Status.Animals” with a dto inside called “User” (making the service WSAUser again)
I understand that other languages don’t support namespaces, but wouldn’t it make more sense for the NativeTypes feature to generate types with names which are the full namespace?
So in F# the user dto would be called “WebServiceAuthenticationUser” ?
Sure I could do this myself by renaming the class to
namespace Web.Service.Authentication
{
public class WebServiceAuthenticationUser : IReturn<WebServiceAuthenticationUserResponse>
{
}
}
just looks bad.
I guess the second part of your answer addresses the ugliness bit - but I’m not sure what the proper solution for web service interoperability is? To make each namespace its own web instance?