Closed GoogleCodeExporter closed 8 years ago
For info, the client/rpc stuff is in progress, and not (AFAIK) in the release
dll. I
will look, though.
Original comment by marc.gravell
on 18 Mar 2009 at 8:48
Applied; thanks for the input; note that the in-progess non-WCF client wont
need
separate proxies (see my blog for why)
Original comment by marc.gravell
on 18 Mar 2009 at 9:22
I understand that RPC support is in progress especially since there is no cross
client standards at the moment. I'll check out your blog.
Original comment by abbott.t...@gmail.com
on 18 Mar 2009 at 10:00
By the way - I applied the patch, but I'm still half-tempted to rename the xslt
arguments to have the "wcf" prefix - i.e. wcfProxy and wcfAsync (or something
like
that). Simply that the implementation is very WCF-specific.
Original comment by marc.gravell
on 18 Mar 2009 at 10:20
The blog entry of note is:
http://marcgravell.blogspot.com/2009/03/explaining-expression.html
Original comment by marc.gravell
on 18 Mar 2009 at 10:22
Not a problem with the wcf stuff. I was half tempted to leave the proxy out of
file
and create a separate xslt myself.
Original comment by abbott.t...@gmail.com
on 19 Mar 2009 at 4:09
That would work too. It is frustrating that the T4 bits aren't standalone until
4.0 -
things might be easier with that as the back-end. Still, it works. It seems
that xslt
isn't a widespread skill, though.
Original comment by marc.gravell
on 19 Mar 2009 at 9:32
Original issue reported on code.google.com by
abbott.t...@gmail.com
on 18 Mar 2009 at 4:38Attachments: