Silverlight WCF Client

[GoogleCodeExporter]

Please include an e-mail address if this might need a dialogue!
==============

What steps will reproduce the problem?
1. Use of the ProtoGen or Plugin VS2K8
2. Generation based on .Proto File
3. Connection to a Java based Webservice with ProtoBuf

What is the expected output? What do you see instead?
A version of CS generated for silverlight without compiler errors

What version of the product are you using? On what operating system?
Visual studio 2K8 on windows 2K3 EE sp2

Please provide any additional information below.
Apparently the global::System.Serializable is not supported in silverlight 3 - 
FW 3.5

I'd like to create a wcf environment, where the protobuf together with a simple 
post, and no 
soap/xml environment is used.  That are the purpose of my developments... 

Original issue reported on code.google.com by esos...@gmail.com on 26 Aug 2009 at 6:41

Attachments:

• [Picture 1.png](https://storage.googleapis.com/google-code-attachments/protobuf-net/issue-70/comment-0/Picture 1.png)

[GoogleCodeExporter]

Oops! Fixed r267
I haven't rebuilt the installer (new laptop OS install not quite ready), but 
the new 
csharp.xslt is here:  
http://protobuf-net.googlecode.com/svn/trunk/ProtoGen/csharp.xslt 

Note that you should specify the lightFramework switch. If you let me know 
whether you 
are using protogen vs VS add-in, I can be more specific.

Original comment by marc.gravell on 26 Aug 2009 at 7:17

• Changed state: Started

[GoogleCodeExporter]

Thanks, for the quick reply.  In the first case, I created the file by the help 
of the VS add-in.  And that one still 
generates a faulty cs file.  By the help of ProtoGen, I was able to generate a 
file that compiled right.  Do you 
have also a suggestion to create a work around in de wcf by the help of a 
basichttpbinding alike interface to 
create simpe webhttp request dat includes as body a protobuf, which I need to 
zip by the way.

Thanks in advance,

Christ.

Original comment by esos...@gmail.com on 26 Aug 2009 at 7:41

[GoogleCodeExporter]

To update the VS add-in, update the file in the install location, typically 
%program 
files%\protobuf-net\protobuf-net-VS9\

Re RPC; if you want to use WCF, then you could pass a byte[] (or better, a 
Stream) on a 
regular WCF contract, and handle the (de)serialization manually. Otherwise, 
there is a 
replacement http-server (no relation to WCF); or I am working on an ASP.NET 
MVC-based 
http server (again, no WCF). Would either of these-help?

Original comment by marc.gravell on 26 Aug 2009 at 7:58

[GoogleCodeExporter]

Exactly, the server has nothing to do with WCF.  But the architect wants me to 
develop it by the help of the 
wcf structure (as a matter of fact he wants that we are able to modify to any 
other service in future, without 
any development, except regeneration of the code, in case we use a real wcf 
service).  So my connection to the 
server is a pure http request "post", with a protobuf block in my body.   The 
files below is the way it 
functionned well, but this is a simple http-request based, the only thing I 
need to do, is format it into a wcf 
alike class.  And it has to be async.

Greetz.,

Christ.

Original comment by esos...@gmail.com on 26 Aug 2009 at 8:14

Attachments:

• dataobjects.cs
• extdataobjects.cs

[GoogleCodeExporter]

OK; and what is the current "gap"? I'll happily help, but I'm unclear what the 
remaining issue(s) is(/are). For the binary-http approach, this is exactly what 
ProtoClient<T> approaches, with 2 *experimental* server implementations; one an 
http-
handler, one MVC based. I've been very busy with other (unrelated) work, but I 
could 
re-prioritise finishing these if they would be helpful.

Original comment by marc.gravell on 26 Aug 2009 at 8:23