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
• The Cake.Core reference should be private. Specifically, your addin's .csproj should have a line similar to this: <PackageReference Include="Cake.Core" Version="0.28.0" PrivateAssets="All" />
• Your addin should target netstandard2.0. Please note that there is no need to multi-target, netstandard2.0 is sufficient.
• There should be a YAML file describing your addin on the cake web site. Specifically, you should add a .yml file in this repo

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 "Project Site" URL is currently pointing to the main Cake repository https://github.com/cake-build/cake. Now that we have documentation on modules on the website, I suggest the project URL to be changed to https://cakebuild.net/extensions/cake-longpath-module/ which goes straight to the docs on this module.

Hi

Getting an issue with this, specifically:

Error: Method 'Move' in type 'Cake.LongPath.Module.LongPathDirectory' from assembly 'Cake.LongPath.Module, Version=0.0.1.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.

Any help would be much appreciated, I can't see the method that needs implementing?

Regards

Hello.

If I use the module Cake.LongPath.Module in my cake scripts, I am not able to use UNC paths. For example:

CleanDirectory(deployDirectory);
// OR
CopyFiles(deployFiles, deployDirectory);

produce an exception

An error occurred when executing task '_deployWeb'.
Error: System.AggregateException: Mindestens ein Fehler ist aufgetreten. ---> System.IO.IOException: Der Vorgang wurde erfolgreich beendet.

   bei Pri.LongPath.Common.ThrowIOError(Int32 errorCode, String maybeFullPath)
   bei Pri.LongPath.FileSystemInfo.Refresh()
   bei Pri.LongPath.DirectoryInfo.get_Exists()
   bei Cake.Common.IO.DirectoryCleaner.Clean(ICakeContext context, DirectoryPath path, Func`2 predicate)
   bei Cake.Common.IO.DirectoryAliases.CleanDirectory(ICakeContext context, DirectoryPath path)
   bei Submission#0.CleanDirectory(DirectoryPath path)
   bei Submission#0.<<Initialize>>b__0_14()
   bei Cake.Core.CakeTaskBuilderExtensions.<>c__DisplayClass20_0.<Does>b__0(ICakeContext x)
   bei Cake.Core.CakeTask.<Execute>d__43.MoveNext()

Without the module, the same works fine.

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

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-module in the NuGet package of this module, so that the NuGet Gallery can display the correct instructions to install this module.

The UI will look similar to this:

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

@devlead 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?

Repro:

Run a cake script with longpath loaded. Will always return "invalid directory". (At least on windows.)

Currently, the Cake.LongPath.Module NuGet Package places all files into the root of the NuGet package:

This needs to be corrected to place them into the appropriate lib folder. In this case lib\net45\

See here: http://docs.nuget.org/ndocs/schema/nuspec#examples

Got this error:

Error: The assembly 'Cake.LongPath.Module, Version=0.4.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)

When #1 is done this should build on appveyor