Silverlight Request And Response location

[Walter Poch]

Hi everyone,

Sorry if this a common question, but I couldn't find a proper solution online, neither on the group. I saw something about a pull request to support portable classes on agatha but it was closed time ago.

The problem: I have one web mvc 4 project who exposes the Service.svc with agatha as usual, but the problem is where to place the Request and Responses so I can share them between the Web and my Silverligth 5 app, so I can configure it as:

new ClientConfiguration(typeof(BuscarClienteRequest).Assembly, typeof(Agatha.Castle.Container)).Initialize();

What is the best practice to locate the Request, in what type of project?,

Thanks in advance!

Walter Poch

[Michael.]

Use a portable class library (http://msdn.microsoft.com/en-ca/library/vstudio/gg597391(v=vs.110).aspx) to share you requests/responses between the client and the server.

Michael.

[Michael.]

Sorry. I replied to that really quickly. It looks like Davy turned down the pull request because it introduced a dependency on the Portable Class Library tools (https://github.com/davybrion/Agatha/pull/21#issuecomment-4300982).  Since the portable class library functionality is now built into VS2012, he might reconsider it....

On Thursday, 14 March 2013 17:31:27 UTC-4, Walter Poch wrote:

[Walter Poch]

Yes, I saw that pull request closed and not applied.

So, for now I'm trying creating two projects, one targeting Silverlight 5 and another .Net 4.0, each one with the same request/response files. I'm not sure if this will work.

2013/3/15 Michael. <michae...@gmail.com>

--
 
---
You received this message because you are subscribed to the Google Groups "agatha" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agatha-rrsl...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Saludos,

Walter G. Poch
--------------------------------------------
Cell: +54 (9 341) 6836871
walte...@gmail.com

[Michael.]

One thing you might do is use the same source files, but "link" them in one of the projects (add -> existing item -> add as link) so they're actually built from the same code...