--- old+++ new@@ -3,7 +3,8 @@
Here are my code snippets;
In Program.cs edit case setup to call the bootstrapper;
-~~~ C#++~~~
case "--setup":
if (!Helper.IsUserElevated())
{
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The idea is good. But two things:
1) I would not mix bootstrapping (or maybe better "prerequisit check") with the libdoc exe detection
2) FindExePath tries to expand the exe name with environment variables. That makes IMHO not much sense. Maybe this function needs to be reworked before it can be integrated
But another idea:
svn.exe is needed only necessary for a few python scripts. But on the other hand, there might be some more prerequisits to check. What's if we don't check it in C# at time of install, but we create a script, named "prerequisits.py", which contains some checks, which can be invoked by all of the other python scripts just on demand.
This will be easier to implement and extend. No need to recompile anything. And in some automated environments, it might make sense to use only some of the commands, where not all of the prerequisits are necessary. So for example, when I only want to operate a jenkins slave, which is exporting documentation, I migth not need SVN.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1) okay, but I only hope that the documentation generation toolchain, at least some commands of it, can be integrated into the cForge tool via some python scripts as this is relatively simple to achieve.
2) findexepath was merely intended as a proof of concept and is by no means a fully finished function. However your idea about "prerequisits.py" is more flexible/extensible then an integrated bootstrapper as you suggested.
3) I now see where your cForge tool will be headed towards. It is a good idea to add a small development-roadmap to this project in order to streamline the idea's towards the intent. Otherwise you might end up with a "swiss army knife" application without a clear goal or purpose. This unless the "swiss army knife" tool is your goal ;-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Honestly?
The swiss army knife is my first intend ;)
But you are right. There are new ideas around for a better integration. After a proof of concept, and a decision, you are right, we can illustrate the goal or roadmap.
For now:
My current Vision is a similar usability as Crossover office is giving the users. You have a set of tools, which can be used by their own. And then you have a frontend, which gives you easy access to the tools for your personal projects.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To make life easier I added the files and the output as attachments
Diff:
The idea is good. But two things:
1) I would not mix bootstrapping (or maybe better "prerequisit check") with the libdoc exe detection
2) FindExePath tries to expand the exe name with environment variables. That makes IMHO not much sense. Maybe this function needs to be reworked before it can be integrated
But another idea:
svn.exe is needed only necessary for a few python scripts. But on the other hand, there might be some more prerequisits to check. What's if we don't check it in C# at time of install, but we create a script, named "prerequisits.py", which contains some checks, which can be invoked by all of the other python scripts just on demand.
This will be easier to implement and extend. No need to recompile anything. And in some automated environments, it might make sense to use only some of the commands, where not all of the prerequisits are necessary. So for example, when I only want to operate a jenkins slave, which is exporting documentation, I migth not need SVN.
1) okay, but I only hope that the documentation generation toolchain, at least some commands of it, can be integrated into the cForge tool via some python scripts as this is relatively simple to achieve.
2) findexepath was merely intended as a proof of concept and is by no means a fully finished function. However your idea about "prerequisits.py" is more flexible/extensible then an integrated bootstrapper as you suggested.
3) I now see where your cForge tool will be headed towards. It is a good idea to add a small development-roadmap to this project in order to streamline the idea's towards the intent. Otherwise you might end up with a "swiss army knife" application without a clear goal or purpose. This unless the "swiss army knife" tool is your goal ;-)
Honestly?
The swiss army knife is my first intend ;)
But you are right. There are new ideas around for a better integration. After a proof of concept, and a decision, you are right, we can illustrate the goal or roadmap.
For now:
My current Vision is a similar usability as Crossover office is giving the users. You have a set of tools, which can be used by their own. And then you have a frontend, which gives you easy access to the tools for your personal projects.