Closed GoogleCodeExporter closed 8 years ago
Well, protogen will create the C#. I suspect it would be hard to separate out
the
logic to create a standalone serializer (i.e. that doesn't need
protobuf-net.dll), so
I'm not sure how achieveable this is under the current design. Worth
consideration,
thouh.
Original comment by marc.gravell
on 17 Dec 2008 at 7:42
I accomplished this in a build script. I use sed to add the .cs file names to a
.csproj file (which is a dll). I then call the dotnet compiler. Unfortunately,
the
import statements inline all of the code so compiling the library will fail.
See
issue 33.
Marc, any word on that issue? Maybe I'll take a crack at this one if it is OK.
Sincerely,
Dave
Original comment by dshrade...@gmail.com
on 10 Jan 2009 at 12:00
I had no plans to address this at the moment.
I'm not sure what the benefit would be over just shipping the protobuf-net dll
and
the domain entity dll, but if you think there is something useful to be gained
- but
could you expand a bit on your cunning plan?
Original comment by marc.gravell
on 10 Jan 2009 at 9:02
Dave: can you clarify which cs lines you mean? Do you mean the protobuf-net
source
.cs? If so, you might want to look at the csproj that are used to build CF etc.
The
problem with this, though, is you'll need the source in the proto-compiler.
If you mean the .cs that is the user's object model, you can do that with
CSharpCodeProvider; look at Generator.cs in the examples/unit-test project
(where for
the unit tests, I check that the generated code compiles).
Original comment by marc.gravell
on 10 Jan 2009 at 9:15
This is a feature of "v2", to be released soon
Original comment by marc.gravell
on 22 Apr 2010 at 9:12
Original comment by marc.gravell
on 22 Apr 2010 at 9:18
Original comment by marc.gravell
on 13 Jun 2011 at 9:05
Original issue reported on code.google.com by
stuor...@gmail.com
on 17 Dec 2008 at 3:18