[antlr-interest] MSBUILD/Vs2008

Jim Idle jimi at temporal-wave.com
Fri Oct 9 15:01:19 PDT 2009

VS is pretty good at just allowing you to exclude file from source code while making them part of the project, I do it all the time. Add to the project, select source control, select remove from source control. Then take a look at the project file to see how it annotates it - I would think that MSBUILD can do that without having to name the files in advance? Or no?

Why does everyone think it is such a good idea to configure build tools with XML? It's a bloody stupid idea.


> -----Original Message-----
> From: Sam Harwell [mailto:sharwell at pixelminegames.com]
> Sent: Thursday, October 08, 2009 5:21 PM
> To: Gavin Lambert; Jim Idle; antlr-interest at antlr.org
> Subject: RE: [antlr-interest] MSBUILD/Vs2008
> I thought about that, but then you run into a problem if you want the
> generated source files visible in your project. As soon as you add the
> files to the project, Visual Studio starts pestering you to add them to
> source control. I don't add the .tokens files to source control, but I
> generally do like having the *Lexer/*Parser.cs files available. I'm
> certainly open to any kind of suggestions (project/MSBUILD targets
> files
> and/or Visual Studio extension ideas for my language service package)
> for easing the integration of grammars into Visual C# projects.
> Sam
> -----Original Message-----
> From: Gavin Lambert [mailto:antlr at mirality.co.nz]
> Sent: Thursday, October 08, 2009 2:23 PM
> To: Sam Harwell; Jim Idle; antlr-interest at antlr.org
> Subject: Re: [antlr-interest] MSBUILD/Vs2008
> At 12:20 8/10/2009, Sam Harwell wrote:
> >*         Create a working Clean target (which
> >carries over to Rebuild). For this to work with
> >source control, I need to make sure that:
> >o   The generated code files are not written to
> >disk if their contents haven't changed.
> >o   The same source file always generates the
> >same output file, which means removing relative
> >paths and timestamps from the comments.
> Or, you know, you could just exclude the
> generated files from source control.  Provided
> that all developers have access to ANTLR (and can
> thus rebuild it) -- which they'd need anyway if
> it's integrated into the project like this --
> then there's no need for the generated files to
> be in source control.  They can just be
> regenerated whenever required.

More information about the antlr-interest mailing list