thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: json protocol for .NET
Date Mon, 13 Apr 2009 01:44:40 GMT
With Maven, we configure the build process to auto-generate if the person
running the build has thrift, but to not do so if they do not.  Thus, I can
check in the generated source as well as the IDL if I change the IDL, but
don't require thrift to run the build.

On Sun, Apr 12, 2009 at 11:37 AM, Debacker <debackerl@gmail.com> wrote:

> 3.      Are there best practice for using code-generation in the build
> > process (in Visual Studio, specifically)?
> >
> > a.      Do you keep the autogenerated server/client code in the source
> > control, or just the IDL?
>
>
> It depends if you auto generate it or not... Usually when someone checkout
> a
> project, the 'standard' build procedure should create the executable file.
> So if your make file (or solution file) generates the source code
> automatically, it would be a bad idea to put these files under version
> control. On the other hand, if this is a manual process, that is only done
> when you decide to upgrade your RPC, make it version controlled.




-- 
Ted Dunning, CTO
DeepDyve

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message