The typescript tsc example does not run every build ( well it runs but checks the files have not changed). The quick and dirty of a seperate project is you can exclude the project from your build so it doesnt get run.
Here is what you want but must be 1 input to 1 output http://msdn.microsoft.com/en-us/library/ms171483.aspx This will do incrementals note VS2012 defaults to incrementals for normal builds so doesnt do it for customs unless you set DISABLEFASTUPTODATECHECK ( but your not using VS2012) <?xml version="1.0" encoding="utf-8"?><Project ToolsVersion="4.0" DefaultTargets="BuildWithExternalTool" xmlns="http://schemas.microsoft.com/developer/msbuild/2003";> <ItemGroup> <ExternalSourceFiles Include="..\ExternalSourceFiles\\*\*.cs" /> <ExternalDll Include="..\ExternalSource\External.dll" /> </ItemGroup> <Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" /> <Target Name="BuildExternalTool" Inputs="@(ExternalSourceFiles);" Outputs="@(ExternalDll)"> <Exec Command="C:\External\Path\To\Tool.exe" /> </Target> <Target Name="BuildWithExternalTool"> <CallTarget Targets="BuildExternalTool" /> <CallTarget Targets="Build" /> </Target></Project> On Sun, Oct 6, 2013 at 7:32 AM, Jonathan S. Shapiro <[email protected]>wrote: > The problem with a prebuild is that it will get done on every build. This > is done because of a bug in VS2008 that has since been fixed. These builds > can now be driven using the normal dependency mechanism. I just don't know > enough about msbuild to know how. > > > On Fri, Oct 4, 2013 at 8:47 PM, Bennie Kloosteman <[email protected]>wrote: > >> If you want a pipeline / make style you have to go to CMake /Nant .. >> pushing msbuild in this direction is asking for pain and I would avoid it >> unless you intend to go no further in this direction. >> >> I think a project with a pre build that calls flex and a C# interface >> around the parser which can then be referenced is worth a shot. It doesnt >> cost much in time and if the style works you have a simple build system. >> >> Ben >> >> _______________________________________________ >> bitc-dev mailing list >> [email protected] >> http://www.coyotos.org/mailman/listinfo/bitc-dev >> >> > > _______________________________________________ > bitc-dev mailing list > [email protected] > http://www.coyotos.org/mailman/listinfo/bitc-dev > >
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
