Target .NET Standard 2.0

and fix the current build warnings:

  Cake.Gulp.csproj: [CCG0005] No reference to 'StyleCop.Analyzers' found. Usage of 'StyleCop.Analyzers' is strongly recommended (see https://cake-contrib.github.io/CakeContrib.Guidelines/rules/ccg0005)
  Cake.Gulp.csproj: [CCG0006] No '.editorconfig' found in folder-structure. Usage of '.editorconfig' is strongly recommended. (see https://cake-contrib.github.io/CakeContrib.Guidelines/rules/ccg0006)
  Cake.Gulp.csproj: [CCG0006] No reference to 'stylecop.json' found. Usage of 'stylecop.json' is strongly recommended. (see https://cake-contrib.github.io/CakeContrib.Guidelines/rules/ccg0006)
  Cake.Gulp.csproj: [CCG0007] Missing suggested target: net5.0 (see https://cake-contrib.github.io/CakeContrib.Guidelines/rules/ccg0007)

The current NuGet.org page looks a bit "empty" without one.

This provides some immediate information that a repository is using
Cake.Recipe, and it is a convention now followed by a number of other
repositories.

See error below:

Cake.exe : Error: Cake.Core.CakeException: The assembly 'Cake.Gulp, Version=0.7.1.0, Culture=neutral, PublicKeyToken=null'
At line:1 char:1
& "C:\projects\requestplex\tools\Cake\Cake.exe" "build.cake" -target= ...

CategoryInfo : NotSpecified: (Error: Cake.Cor...KeyToken=null' :String) [], RemoteException
FullyQualifiedErrorId : NativeCommandError

is referencing an older version of Cake.Core (0.17.0).
This assembly need to reference at least Cake.Core version 0.22.0.
Another option is to do
wngrade Cake to an earlier version.
It's not recommended, but you can explicitly opt-out of assembly verification
by configuring the Skip Verification setting to true
(i.e. command line parameter "--settings_skipverification=true",
envrionment variable "CAKE_SETTINGS_SKIPVERIFICATION=true",
read more about configuration at https://cakebuild.net/docs/fundamentals/configuration)
at Cake.Core.Reflection.AssemblyVerifier.Verify(Assembly assembly)
at Cake.Core.Reflection.AssemblyLoader.Load(FilePath path, Boolean verify)
at Cake.Core.Scripting.ScriptRunner.Run(IScriptHost host, FilePath scriptPath, IDictionary`2 arguments)
at Cake.Commands.BuildCommand.Execute(CakeOptions options)
at Cake.CakeApplication.Run(CakeOptions options)
at Cake.Program.Main()
Command executed with exc

I was able to work around this by using the --settings_skipverification=true argument like the error states. But thought you'd need to know this :)

The NuGet Gallery will soon include a "Cake" tab with instructions on how to use NuGet packages in Cake build scripts. I'd like to suggest that you include the tag cake-addin in the NuGet package of this addin, so that the NuGet Gallery can display the correct instructions to install this addin.

The UI will look similar to this:

Documentation on best practices on tags for Cake addins: https://cakebuild.net/docs/extending/addins/best-practices#tags

We performed an automated audit of your Cake addin and found that it does not follow all the best practices.

We encourage you to make the following modifications:

• You are currently referencing Cake.Core 0.28.0. Please upgrade to 0.33.0
• The nuget package for your addin should use the cake-contrib icon. Specifically, your addin's .csproj should have a line like this: <PackageIconUrl>https://cdn.jsdelivr.net/gh/cake-contrib/graphics/png/cake-contrib-medium.png</PackageIconUrl>.

Apologies if this is already being worked on, or if there are existing open issues, this issue was created based on what is currently published for this package on NuGet.

This issue was created by a tool: Cake.AddinDiscoverer version 3.12.1

Build against Cake 1.0

We should pin Cake.Recipe to 1.0.0 to avoid breaking build

Looks like a bug in the MSBuild of cake. Upping the cake version in packages.config to 0.21.0 fixed it.

We performed an automated audit of your Cake addin and found that it does not follow all the best practices.

We encourage you to make the following modifications:

• You are currently referencing Cake.Core 0.26.0. Please upgrade to 0.28.0
• Your addin should target netstandard2.0. Please note that there is no need to multi-target, netstandard2.0 is sufficient.

Apologies if this is already being worked on, or if there are existing open issues, this issue was created based on what is currently published for this package on NuGet.org and in the project on github.

The Discussion platform for Cake-Contrib has been moved from Gitter to GitHub Discussion (see cake-build/website#1470).
Please check this repo for references to Gitte and replace them accordingly.

Search suggests that references could be in

• README.md
• docs/input/blog/new-release-0.7.0.md

Thanks again for creating this Cake Addin, we really appreciate the effort that you have put in to creating it.

We, the Cake Team, recently announced a new Cake Contrib Icon, details of which can be found here:

http://cakebuild.net/blog/2017/06/new-cake-contrib-icon

Would you consider changing the nuspec file for your NuGet Package to use this new Cake Contrib Icon? If so, the recommended URL to use is:

https://cdn.rawgit.com/cake-contrib/graphics/a5cf0f881c390650144b2243ae551d5b9f836196/png/cake-contrib-medium.png

Details of the above URL can be found in the repository here:

https://github.com/cake-contrib/graphics

Please let me know if you have any questions.

Build against Cake 0.28.0

Cake 2.0.0 has been released 🎉

https://github.com/cake-contrib/Cake.Gulp/blob/develop/nuspec/nuget/Cake.Gulp.nuspec#L12

This should include .git at the end, as per conversation with Anand from NuGet Team:

https://twitter.com/adgrv/status/1127591787697061888

When setting WorkingDirectory and running build.ps1 get error: No gulpfile found

Without setting WorkingDirectory, gulpfile is found, but then node_modules are not found (looks in parent directory for node_modules)
module.js:471
throw err;
^

Error: Cannot find module 'C:\xxx\node_modules\gulp\bin\gulp.js'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3

We performed an automated audit of your Cake addin and found that it does not follow all the best practices.

We encourage you to make the following modifications:

• You are currently referencing Cake.Core 0.28.0. Please upgrade to 0.33.0
• The nuget package for your addin should use the cake-contrib icon. Specifically, your addin's .csproj should have a line like this: <PackageIconUrl>https://cdn.jsdelivr.net/gh/cake-contrib/graphics/png/cake-contrib-medium.png</PackageIconUrl>.

Apologies if this is already being worked on, or if there are existing open issues, this issue was created based on what is currently published for this package on NuGet.

This issue was created by a tool: Cake.AddinDiscoverer version 3.12.1

Use embedded icon in NuGet package

Current versions of Cake.Recipe require Cake >= 0.28.0

Hi!

I forked your reposistory to extend/fix functionality and stumbled across a bug.

Source file 'C:\Projects\cake-gulp\src\Cake.Gulp..\VersionAssemblyInfo.cs' could not be found.

current version is 2.2.1, there is a migration-path.

We've recently released new icons for Cake extensions, to help more easily differentiate Cake Addins, Modules, Recipes, etc.

More information: https://github.com/cake-contrib/graphics

Hi,

Nice to see a plugin for Gulp! 👍

I found out that the global execution of grunt did not evaluate arguments as the local one did.
I forked your repository and added the evaluation and then I was able to specify a path to my gulpfile and everything worked as expected.

Here is my fix: nengberg@15b9f9b

Am I correct or is there another way in solving this? Otherwise, would you like me to open a pull request for this one?

Best Regards
NIklas

I need to set the path to nodejs to prevent it from using the one that is shipped with VStudio.
E.g. add the method below to: "GulpLocalRunnerSettings" class.

public GulpLocalRunnerSettings SetToolPath(FilePath toolPath) { ToolPath = toolPath; return this; }

Best regards,
Kevin

We performed an automated audit of your Cake addin and found that it does not follow all the best practices.

We encourage you to make the following modifications:

• You are currently referencing Cake.Core 0.28.0. Please upgrade to 0.33.0
• The nuget package for your addin should use the cake-contrib icon. Specifically, your addin's .csproj should have a line like this: <PackageIconUrl>https://cdn.jsdelivr.net/gh/cake-contrib/graphics/png/cake-contrib-medium.png</PackageIconUrl>.

Apologies if this is already being worked on, or if there are existing open issues, this issue was created based on what is currently published for this package on NuGet.

This issue was created by a tool: Cake.AddinDiscoverer version 3.12.1

@Philo I am pretty much at the point where my not so secret project, Cake.Recipe, is ready to be rolled out.

Would you be interested in me adding it to this repository?

The benefits would be...

• a single place to control all the builds in the cake-contrib organisation
• access to notifications on twitter and gitter when new releases are available

Things that Cake.Recipe already does:

• Version with GitVersion
• Build
• Compile
• Run Unit Tests
• Submit results to coveralls.io
• NuGet Package everything
• Upload all artifacts to AppVeyor
• Runs DupFinder
• Runs InspectCode
• Handles publishing to both MyGet and NuGet (for interim releases)
• Runs GitLink, meaning that addin code is debuggable doing debug session in visual studio when debugging build.cake
• Documentation Website generation using Wyam

Probably other stuff that I have forgotten.

The main thing being, if we add something to Cake.Recipe, then all projects that are already using Cake.Recipe should be able to immediately take advantage of it.

Thoughts? If you were interested, would you be happy to have me make the changes directly to repo, or would you prefer it as a PR?

If the gulp tasks produce any errors, it doesn't seem to get reported back to cake so the build continues on and the CI server treats it as a successful build. I don't see anything in the source that checks for the status of the command. Is there a way to trap these errors and fail the build using this extension?

The current nuget available for Cake.Gulp is breaking after yesterday's Cake.Core upgrade to 0.26.0.
Getting the following error:

Error: The assembly 'Cake.Gulp, Version=0.8.0.0, Culture=neutral, PublicKeyToken=null'
is referencing an older version of Cake.Core (0.22.0).
This assembly need to reference at least Cake.Core version 0.26.0.
Another option is to downgrade Cake to an earlier version.
It's not recommended, but you can explicitly opt-out of assembly verification
by configuring the Skip Verification setting to true
(i.e. command line parameter "--settings_skipverification=true",
environment variable "CAKE_SETTINGS_SKIPVERIFICATION=true",
read more about configuration at https://cakebuild.net/docs/fundamentals/configuration)