We call Gulp from our csproj , since we are using Visual Studio 2013 for this project:
<Target Name="AfterBuild"> <Exec Command="gulp" /> </Target>
However, since we are still developing this new project, we often extend gulpfile.js to include new packages. The developer will do, for example. npm install gulp-util --save-dev and write a new task, and all is well.
Then the developer checks gulpfile.js and packages.json for our VCS. Currently:
- Teamcity has an extra build step of
npm install ; - Each developer must run
npm install manually;
To remember what needs to be done manually is not a great place. At some point, we had it in our csproj file inside Task ...
<Exec command="npm install" />
... immediately before gulp exec, so the developers couldn’t forget to complete this manual step. However, this may take one or even several seconds for each assembly (re), which is annoying.
Is there a better way to solve this problem? How do you handle packages.json updates in projects where large (ish) teams are developed using Visual Studio?
source share