Initalize Cake Command

[Seeker1437]

The idea is to be able to open a possibly pre-existing solution and then right click and select 'Initialize Cake'.

Using a gui and user input it would give you the ability to have the properly files generated for you.

In the backend it might create and add a cake script project placing the files were the user likes, where they can then edit and debug the scripts from there, but it may use the user input to add certain switches pr argument that may alter the behavior of cake initially.

I hope I explained well :D.

[agc93]

Thanks for the suggestion @Seeker1437

As an introduction and context, we currently include an item template for a new Cake script that can be added to a project, as well as the Install commands available in the Build > Cake Build menu group (for bootstrappers and configuration files).

So that we're on the same page, it sounds like you're looking for very similar functionality to what's included currently, but with the addition of generating the contents of the script based on user input, rather than just including a blank template. Am I understanding you correctly?

Happy to hear any more ideas on how you see this experience working from a user perspective.

[gep13]

@Seeker1437 were you able to expand on this suggestion that you made? Thanks!

[Seeker1437]

Hi, @agc93 , Thank you for your time!

You understand correctly!

The idea is to help standardize certain aspects of cake in certain situations, the builder (as I can imagined) would provide the user with the opportunity to make adjustments to the file via a series of options in which a preview can be generated during the process per changed. The each option can then be explained and recommendations from the cake devs themselves are available at a basic level. The application can then point users to the Wiki for more in depth scenarios.

The idea is that I believe what we have is wonderful and such not leave, but I like the idea of also having an option that does all three, with the option of being blank or being filled out with information generated from a wizard or something like it to increase adoptability and for convenience.

I see it helping with a few things:

• Possibly detecting unit tests and automatically adding the requires addins and tools to run those tests.
• Possibly help with Nuspec definitions
• Possibly help with the configuration of different tasks and their dependancies and conditions.
• Possible visual management of addins and tools
• Possible for easy entry into the world of Cake
• Suggested configurations for different compilers that ensure builds on all platforms (if possible) is successful

It's totally optional, as a forewarning, I often come up with ideas that may require mpre effort than most people are willing to make, and I don't mean to say you guys wouldn't do it if you didn't believe it in, but because this software is so powerful, and with the idea of getting that many more people using it, I feel this is really important form of... outreach and that official support for something like this from Cake is a nice it will let users know you will that extra mile to get them onboard (though in your case word of mouth is super strong, but it doesn't hurt.)

[soroshsabz]

ITNOA

I think it is great feature and more like Epic :)