Post by i-campbell on #21 Future of cforge package ^{CODESYS Forge tickets (Post)}
I have kind of been thinking on this on and off, so haven't until now commented. My view was to look at: 1. what types of cForge users exist, 2. what skills they may have / may lack, 3. and then what tasks each type of cForge users should want to perform. It is my opinion that open source development and its associated workflows are new to many automation engineers. I think the short term development of the cForge tool should focus on guiding the user to complete tasks. Types of users: 1.a admin role for forge. 1.b Contribute new projects intending others to contribute. 1.c Contribute new projects with no intent to seek contributions. 1.d Contribute code to existing projects. 1.e Contribute non-code to existing projects, such as documentation or issue management. 1.f Take some existing code and modify it but don't contribute. 1.g Wanting to spend as little time in forge as possible, just wanting to grab the driver or lib they want. 1.h Just wanting to talk on the forum. Skill/Experience I think that some people will have varying levels of each of these skills: 2.a Computer programming 2.b Version control systems 2.c Testing 2.d CODESYS 2.e PLCs 2.f open source communities and issues 2.g Electronics 2.h Physical applications Tasks and workflows So for me the cForge tool should be aimed at users 1.b through 1.e (hereafter referred to as contributors). The main goal is to help contributors to make their projects as accessible as they want it to be for users 1.f through 1.g (hereafter referred to as audience). A secondary goal is to help the contributors make their projects easier to contribute to. So we have the documentation [forge:wiki:Home] which describes some workflows. Should CODESYS be a prerequisite? Well, what if the project doesn't have any CODESYS code? for example an open source python script to test modbus comms or something? So I think the very first getting started step is install cforge.exe. Then I would like cforge to have a developer readiness checklist: - Install CODESYS IDE (link to https://store.codesys.com/codesys.html, or maybe link to a forge page with some installation tips and tricks? both?) - Install SVN (link to store or forge) - Install Tortise SVN - Install cforge.package (will be seperate to cforge.exe) - Set path variables - Link to OAuth credentials - etc. The checkboxes can be marked by the contributor as TO DO, WON'T DO, NOT PLANNED, DONE etc. Maybe a bonus if we can autodetect some of them like isCODESYSInstalled. Then there will be some workflows, once the developer is satisfied with their PC's readiness: * Start new forge project - Driver project, lib project, hack? - Just under my user page for now? or on the main directory? - do you have files already, or do you want a blank folder to start with? Link existing forge project Then there will be a project readiness checklist, similar to the development machine readiness checklist. * SVN or Git repository created * If you're at work, do you have permission from your boss to open source this? * used external libs correctly (link to info on maintaining copyright etc) * extended someone else's work correctly (link to info) * License selected and added (link to help on selecting a license) * Is there a readme.md (button to create one and open in text editor) * Is there contrib guidelines * Package Manifest exist (button to create one) * Package exist (button to create one) * package uploaded to forge.codesys.com * Wiki exists on forge.codesys.com * Link exists on the Project Home page of project to download package * Link exists on the Project Home page to discuss project in forum (or maybe search forum for discussions related to the project) * etc. Perhaps a button to initiate a check for some of these things. For instance it could check if the manifest is up to date, or if the package installs successfully. Each task could have a "search for topic in forge docu / forge forum / help.codesys.com / google". A "Discuss topic in forum" button could create a Nicely formatted Discussion topic, with some key info already filled in, eg. cForge version, codesys version, cForge workflow item, Developer readiness %?. It may even have a template such as some subheadings [Background] [Question] Anyway thanks for listening to my rambling. If this direction for cForge is of interest I am happy to contribute further.
Last updated: 2020-02-02

Post by ingo on #21 Future of cforge package ^{CODESYS Forge tickets (Post)}
Proposal: We plan a jitsi meeting to discuss and priorize this stuff. What do you think?
Last updated: 2020-04-09

Post by i-campbell on #14 create Package bug ^{CODESYS Forge tickets (Post)}
I think the "pull request" workflow at the moment is as follows: 1. create a ticket 2. Checkout 3. Make changes 4. Test changes 5. Upload the changed files to the ticket and say "dear maintainer, please accept this change because...". It's in the documentation somewhere. OK, I will make the change and test. Will have to wait until next week.
Last updated: 2020-01-18

Post by aliazzz on #21 Future of cforge package ^{CODESYS Forge tickets (Post)}
Hi, just some thoughts: GIT integration for cForge (and a plugin for GIT in CODESYS IDE?) would be very very favourable! Extend cForge with Webhooks to let any builder (arbitrairly which or where) start a job very cool! Generating .CHM and or .PDF documentation (with choice of a few cool prefab documentation frames) from the reSructured text in a project or Library Letting cForge Tool run a custom user made script from windows explorer with a right click (an "execute custom" command). What the script itself does is up to the user, as long as it combines cForge and CODESYS in python.
Last updated: 2020-01-18

Post by aliazzz on #8 cForge installation on latest Win10 x64 ^{CODESYS Forge tickets (Post)}
Extra feedback; I have had Turtoise SVN installed before I installed the CODESYS cForge & SVN package (!) Still, I will check the windows environment variables (paths) and your other tips.
Last updated: 2018-12-31

Post by aliazzz on #15 renaming cforge commands ^{CODESYS Forge tickets (Post)}
The cForge package 1.0.0.15 in the trunk has not been touched for almost a year? But I have seen the renamed commands but I am still using this year old version. Also, my own knowledge on SVN/Git has increased ever since, still I am in no way an expert yet! ;-)
Last updated: 2020-01-18

Post by ingo on #13 Automatic Build ^{CODESYS Forge tickets (Post)}
status: open --> pending assigned_to: Ingo
Last updated: 2019-04-20

Post by erichspitzweg on #1 Implement URL Handler and framework for actions ^{CODESYS Forge tickets (Post)}
status: open --> accepted
Last updated: 2018-03-20

Post by ingo on #29 CFORGE Tool doesn't work with SP16 ^{CODESYS Forge tickets (Post)}
It is in fact more an integration issue, as the script didn't work with the newest version. And currently it's hard to test, as codesys-4-linux still doesn't support CODESYS SVN 😞
Last updated: 2020-08-11

Post by erichspitzweg on #4 Package Installation doesn't always work ^{CODESYS Forge tickets (Post)}
status: accepted --> closed
Last updated: 2018-04-17

Post by aliazzz on #29 CFORGE Tool doesn't work with SP16 ^{CODESYS Forge tickets (Post)}
Never noticed this... > haven't tested it :-| maybe you should add some unit test for this in the package?
Last updated: 2020-08-11

Post by ingo on #25 Cannot find Product News ^{CODESYS Forge tickets (Post)}
That's right. The reason is, that all special categories in the App are able to trigger push notifications. And the idea was, that the product news would also be of interest for the typical forge user. Despite this, there is no reason why we should duplicate this information on the forge website.
Last updated: 2020-02-21

Post by aliazzz on #14 create Package bug ^{CODESYS Forge tickets (Post)}
I cannot try it out any more, but in hindsight, without even trying your suggestion I'd say point 2 is valid. Whenever spaces are present in a windows path, one must open and close the entire string with surrounding quotes. So It should be: "%V".
Last updated: 2020-01-18

Post by erichspitzweg on #16 Where can I find the version number for Android app? ^{CODESYS Forge tickets (Post)}
assigned_to: erichspitzweg
Last updated: 2019-12-30

Post by i-campbell on #14 create Package bug ^{CODESYS Forge tickets (Post)}
CWD is Current Working Directory as seen by the cforge c# application. This is where the context menu is setup for the create package https://forge.codesys.com/tol/cforge/code/HEAD/tree/trunk/cforge/cforge/Package/CFORGE/Setup.reg#l62 So it will be calling : cmd /C cforge.exe --create-package C:\Users\user\Desktop\I2C mcp7941x Code for cforge.exe is here: https://forge.codesys.com/tol/cforge/code/HEAD/tree/trunk/cforge/cforge/Program.cs So it can be seen it then passes those two arguments to the python script here: https://forge.codesys.com/tol/cforge/code/HEAD/tree/trunk/cforge/cforge/Package/CFORGE/Scripts/create-package.py# Using this helper function: https://forge.codesys.com/tol/cforge/code/HEAD/tree/trunk/cforge/cforge/Helper.cs#l251 Ideally we only need to fix the setup.reg, so I think steps are: 1. Does it work if you open a cmd prompt and navigate to the directory, then type the command: cforge.exe --create-package "C:\Users\user\Desktop\I2C mcp7941x" 2. If yes fix the setup.reg to put quotes around %V 3. If not, investigate further
Last updated: 2020-01-18

Ticket #1: Implement URL Handler and framework for actions ^{CODESYS Forge tickets (Ticket)}
The idea is, that we first create a framework in C#, with the following features: Implements an URL handler Parses the command line, as well as URLs, and prepares it for the "actions" call "commands", based on the command that was passed to the URL, or "cforge" on the command line This way, the command can be implemented easyly and transparent in python scripts. We can then sub-group further to different actions, which need to be performed in several commands. We are using the scripting assemblies from CODESYS installation. cforge will be installed in form of a CODESYS package into CFORGE subfolder in <ap_root folder=""> (next to "Common" etc.). In main folder will be the cforge.exe and a Batch file to trigger the URL handler registration. In a subfolder "Scripts" are all the IPY scripts (like 2nd level commands for the cforge "tool world").</ap_root> Implement URL Handler and framework for actions CODESYS Forge 0 tickets Ticket tickets Implement URL Handler and framework for actions 2018-04-11 17:38:57.993000 closed False 0 ingo Ticket #1: Implement URL Handler and framework for actions 0 1.0 False /tol/cforge/tickets/1/ erichspitzweg 2018-03-16 06:40:29.728000 None 1 cforge The idea is, that we first create a framework in C#, with the following features: Implements an URL handler Parses the command line, as well as URLs, and prepares it for the "actions" call "commands", based on the command that was passed to the URL, or "cforge" on the command line This way, the command can be implemented easyly and transparent in python scripts. We can then sub-group further to different actions, which need to be performed in several commands. We are using the scripting assemblies from CODESYS installation. cforge will be installed in form of a CODESYS package into CFORGE subfolder in <ap_root folder=""> (next to "Common" etc.). In main folder will be the cforge.exe and a Batch file to trigger the URL handler registration. In a subfolder "Scripts" are all the IPY scripts (like 2nd level commands for the cforge "tool world").</ap_root> False False 5
Last updated: 2018-04-11

Ticket #2: commit: Implement the action 'commit' ^{CODESYS Forge tickets (Ticket)}
The commit action does several at once: Export Documentation The script uses the PLCopen Export to get the content out of the project. Then it transforms the result into Markdown, using XSLT. First, it is more than enough to support ST. Commit with CODESYS SVN Commit the changes in the project with CODESYS SVN to the repository that is connected with it (no changes done). Commit with local SVN Add / commit the project file and exported documentation, using external SVN client.commit: Implement the action 'commit' CODESYS Forge 0 tickets Ticket tickets commit: Implement the action 'commit' 2018-08-09 20:24:11.274000 closed False 1 ingo Ticket #2: commit: Implement the action 'commit' 1 1.0 False /tol/cforge/tickets/2/ ingo 2018-03-16 06:47:17.256000 None 2 cforge The commit action does several at once: Export Documentation The script uses the PLCopen Export to get the content out of the project. Then it transforms the result into Markdown, using XSLT. First, it is more than enough to support ST. Commit with CODESYS SVN Commit the changes in the project with CODESYS SVN to the repository that is connected with it (no changes done). Commit with local SVN Add / commit the project file and exported documentation, using external SVN client. False False 3
Last updated: 2018-08-09

Ticket #3: Repository handling ^{CODESYS Forge tickets (Ticket)}
The repository handling is one of the most trickiest parts of this projects. In a discussion with erichspitzweg, we discovered the following: Instlalled packages need to be tracked locally, as the information can't get easily out of the CODESYS Package Management The available packages can be served either by a full repository list (like in debian), or in a distributed way (like with npm). When doing it distributed, we could use (as an option) the project url (e.g. 'tol/cforge') as the base URI to find the manifests of dependent packages With this ticket, the following commands should be implemented: list install removeRepository handling CODESYS Forge 0 tickets Ticket tickets Repository handling 2018-03-16 10:31:49.572000 open False 0 ingo Ticket #3: Repository handling 0 1.0 False /tol/cforge/tickets/3/ None 2018-03-16 06:57:45.881000 None 3 cforge The repository handling is one of the most trickiest parts of this projects. In a discussion with erichspitzweg, we discovered the following: Instlalled packages need to be tracked locally, as the information can't get easily out of the CODESYS Package Management The available packages can be served either by a full repository list (like in debian), or in a distributed way (like with npm). When doing it distributed, we could use (as an option) the project url (e.g. 'tol/cforge') as the base URI to find the manifests of dependent packages With this ticket, the following commands should be implemented: list install remove False False 1
Last updated: 2018-03-16

Ticket #4: Package Installation doesn't always work ^{CODESYS Forge tickets (Ticket)}
On some systems, there is no default application registered for *.package files. On those systems the installation through cforge doesn't work.Package Installation doesn't always work CODESYS Forge 0 tickets Ticket tickets Package Installation doesn't always work 2018-04-17 18:47:37.312000 closed False 0 ingo Ticket #4: Package Installation doesn't always work 0 1.0 False /tol/cforge/tickets/4/ erichspitzweg 2018-04-16 16:20:12.859000 None 4 cforge On some systems, there is no default application registered for *.package files. On those systems the installation through cforge doesn't work. False False 3
Last updated: 2018-04-17

Ticket #5: Implement checkout ^{CODESYS Forge tickets (Ticket)}
Implementierung a basic cforge checkout action, which checks out CODESYS libraries and projects, and can be used in combination with the links on the websiteImplement checkout CODESYS Forge 0 tickets Ticket tickets Implement checkout 2018-05-15 22:22:30.654000 closed False 0 ingo Ticket #5: Implement checkout 0 1.0 False /tol/cforge/tickets/5/ ingo 2018-05-09 23:36:12.124000 None 5 cforge Implementierung a basic cforge checkout action, which checks out CODESYS libraries and projects, and can be used in combination with the links on the website False False 4
Last updated: 2018-05-15

Ticket #6: support context menu entry for common use cases in windows explorer ^{CODESYS Forge tickets (Ticket)}
It is simple to add context menu entries (even with sub-menu and icons). So it would be very convenient to use cforge directly from windows explorer. support context menu entry for common use cases in windows explorer CODESYS Forge 0 tickets Ticket tickets support context menu entry for common use cases in windows explorer 2018-08-09 19:29:35.780000 closed False 0 erichspitzweg Ticket #6: support context menu entry for common use cases in windows explorer 0 1.0 False /tol/cforge/tickets/6/ ingo 2018-06-04 18:39:31.934000 None 6 cforge It is simple to add context menu entries (even with sub-menu and icons). So it would be very convenient to use cforge directly from windows explorer. False False 2
Last updated: 2018-08-09

Ticket #7: Avoid warnings from URL handlers ^{CODESYS Forge tickets (Ticket)}
There are two warnings produced when clicking on an URL handler: Warning from the browser, that an external App is launched. This needs to be disabled per browser: IE Execute as Admin This needs to be avoided in the tool, which doesn't need to have admin rights.Avoid warnings from URL handlers CODESYS Forge 0 tickets Ticket tickets Avoid warnings from URL handlers 2018-08-09 19:28:40.935000 closed False 0 ingo Ticket #7: Avoid warnings from URL handlers 0 1.0 False /tol/cforge/tickets/7/ ingo 2018-06-04 20:17:53.964000 None 7 cforge There are two warnings produced when clicking on an URL handler: Warning from the browser, that an external App is launched. This needs to be disabled per browser: IE Execute as Admin This needs to be avoided in the tool, which doesn't need to have admin rights. False False 2
Last updated: 2018-08-09

Ticket #8: cForge installation on latest Win10 x64 ^{CODESYS Forge tickets (Ticket)}
Hi, It seems that the cForge package does not work correct on my (virtual) x64 devbox. The package itself installs to path "C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE" However, the setup.bat in that directory will not run correct as it returns; "Setup cforge" The system cannot find the file C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE\cforge.exe --setup. Press any key to continue . . . Offcourse I tried to edit the path in the .bat file with elevated rights but it had no effect. Also, manually merging the setup.reg seems to work, but when I use the Checkout Function, all seems fine, however after some time the commandline starts to tell me that it cannot find SVN: [INFO] Executing: C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE\Scripts\checkout.py *--checkout https://forge.codesys.com/svn/drv,mega-io,code/ CWD: C:\Users\user\AppData\Local\Chromium\Application\71.0.3578.98 User elevated: False default case: --checkout [INFO] Executing: C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE\Scripts\checkout.py C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE\Scripts\action.svn.checkout.py running codesys with script C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE\Scripts\action.svn.checkout.py test 'svn' is not recognized as an internal or external command, operable program or batch file. 'svn' is not recognized as an internal or external command, operable program or batch file. 'svn' is not recognized as an internal or external command, operable program or batch file. done: 0 cforge finished. ----------------------------------------------------------------------------* cforge -v returns v1.0.0.0 while the package is version itself is v1.0.0.11 Can you give me some hints on how to correctly activate cForge? cForge installation on latest Win10 x64 CODESYS Forge 0 tickets Ticket tickets cForge installation on latest Win10 x64 2019-01-13 14:34:44.145000 closed False 0 aliazzz Ticket #8: cForge installation on latest Win10 x64 0 1.0 False /tol/cforge/tickets/8/ codesys-com 2018-12-30 22:03:28.727000 None 8 installation of cForge on x64 machines cforge Hi, It seems that the cForge package does not work correct on my (virtual) x64 devbox. The package itself installs to path "C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE" However, the setup.bat in that directory will not run correct as it returns; "Setup cforge" The system cannot find the file C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE\cforge.exe --setup. Press any key to continue . . . Offcourse I tried to edit the path in the .bat file with elevated rights but it had no effect. Also, manually merging the setup.reg seems to work, but when I use the Checkout Function, all seems fine, however after some time the commandline starts to tell me that it cannot find SVN: [INFO] Executing: C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE\Scripts\checkout.py *--checkout https://forge.codesys.com/svn/drv,mega-io,code/ CWD: C:\Users\user\AppData\Local\Chromium\Application\71.0.3578.98 User elevated: False default case: --checkout [INFO] Executing: C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE\Scripts\checkout.py C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE\Scripts\action.svn.checkout.py running codesys with script C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE\Scripts\action.svn.checkout.py test 'svn' is not recognized as an internal or external command, operable program or batch file. 'svn' is not recognized as an internal or external command, operable program or batch file. 'svn' is not recognized as an internal or external command, operable program or batch file. done: 0 cforge finished. ----------------------------------------------------------------------------* cforge -v returns v1.0.0.0 while the package is version itself is v1.0.0.11 Can you give me some hints on how to correctly activate cForge? False False 2
Last updated: 2019-01-13

Ticket #9: Draft for better bootstrapping and checking prerequisits ^{CODESYS Forge tickets (Ticket)}
I extended cForge helper class with a bootstrapper to detect SVN installation and to add the LibDoc.exe to the PATH environmentvariables. Offcourse its written in similair style to the excisting code. Here are my code snippets; In Program.cs edit case setup to call the bootstrapper; case "--setup": if (!Helper.IsUserElevated()) { Console.WriteLine("[INFO] Setup URL Handler and add tool to path. "); Helper.RunElevated("--setup"); } else { /// bootstrapper Helper.bootstrap(bDebug); Helper.RegisterProtocol(bDebug); Helper.AddToSystemPath(bDebug); } break; And extend SystemPath region in Helper.cs with Bootstrapper; #region SystemPath public static void AddToSystemPath(bool bVerbose) { string strPath = System.Environment.GetEnvironmentVariable("Path", EnvironmentVariableTarget.Machine); string[] split = strPath.Split(new Char[] { ';' }); string path = Path.GetDirectoryName(GetCFORGEAssemblyPath()); string strNewSystemPath = strPath + ";" + path; if (!split.Contains(path)) { System.Environment.SetEnvironmentVariable("Path", strNewSystemPath, EnvironmentVariableTarget.Machine); } } public static void bootstrap(bool bVerbose) { /// bootstrapper /// warning for svn.exe if not present string exepath = Helper.FindExePath("svn.exe"); if (exepath == String.Empty) { Console.WriteLine("[WARNING] Please install Turtoise SVN with command line client option!"); } else { Console.WriteLine("[INFO] Turtoise SVN detected. \r\n\tPath is: " + exepath); exepath = String.Empty; } /// add libdoc.exe to path to enable CODESYS libdocscripting (TODO expand this section) exepath = Helper.FindExePath("libdoc.exe"); string strPath = System.Environment.GetEnvironmentVariable("Path", EnvironmentVariableTarget.Machine); string path = String.Empty; string strNewSystemPath = String.Empty; if (exepath == String.Empty) { /// add path to: "C:\Program Files\CODESYS 3.5.14.0\CODESYS\DocScripting\3.5.14.0" /// for now quick and dirty => should become dynamic path = "C:\\Program Files\\CODESYS 3.5.14.0\\CODESYS\\DocScripting\\3.5.14.0"; strNewSystemPath = strPath + ";" + path; System.Environment.SetEnvironmentVariable("Path", strNewSystemPath, EnvironmentVariableTarget.Machine); Console.WriteLine("[INFO] Environmentvariable for DocScripting added: \r\n\tPath is: " + path); } else { Console.WriteLine("[INFO] DocScripting detected. \r\n\tPath is: " + exepath); exepath = String.Empty; } } /// <summary> /// Expands environment variables and, if unqualified, locates the exe in the working directory /// or the evironment's path. /// </summary> /// <param name="exe">The name of the executable file</param> /// <returns>The fully-qualified path to the file</returns> /// <exception cref="System.IO.FileNotFoundException">Raised when the exe was not found</exception> public static string FindExePath(string exe) { exe = Environment.ExpandEnvironmentVariables(exe); if (!File.Exists(exe)) { if (Path.GetDirectoryName(exe) == String.Empty) { foreach (string test in (Environment.GetEnvironmentVariable("PATH") ?? "").Split(';')) { string path = test.Trim(); if (!String.IsNullOrEmpty(path) && File.Exists(path = Path.Combine(path, exe))) return Path.GetFullPath(path); } } return String.Empty; /// throw new FileNotFoundException(new FileNotFoundException().Message, exe); } return Path.GetFullPath(exe); } #endregion Draft for better bootstrapping and checking prerequisits CODESYS Forge 0 tickets Ticket tickets Draft for better bootstrapping and checking prerequisits 2019-12-03 04:19:15.473000 open False 0 aliazzz Ticket #9: Draft for better bootstrapping and checking prerequisits 0 1.0 False /tol/cforge/tickets/9/ None 2019-01-05 17:03:50.158000 None 9 region endregion cforge I extended cForge helper class with a bootstrapper to detect SVN installation and to add the LibDoc.exe to the PATH environmentvariables. Offcourse its written in similair style to the excisting code. Here are my code snippets; In Program.cs edit case setup to call the bootstrapper; case "--setup": if (!Helper.IsUserElevated()) { Console.WriteLine("[INFO] Setup URL Handler and add tool to path. "); Helper.RunElevated("--setup"); } else { /// bootstrapper Helper.bootstrap(bDebug); Helper.RegisterProtocol(bDebug); Helper.AddToSystemPath(bDebug); } break; And extend SystemPath region in Helper.cs with Bootstrapper; #region SystemPath public static void AddToSystemPath(bool bVerbose) { string strPath = System.Environment.GetEnvironmentVariable("Path", EnvironmentVariableTarget.Machine); string[] split = strPath.Split(new Char[] { ';' }); string path = Path.GetDirectoryName(GetCFORGEAssemblyPath()); string strNewSystemPath = strPath + ";" + path; if (!split.Contains(path)) { System.Environment.SetEnvironmentVariable("Path", strNewSystemPath, EnvironmentVariableTarget.Machine); } } public static void bootstrap(bool bVerbose) { /// bootstrapper /// warning for svn.exe if not present string exepath = Helper.FindExePath("svn.exe"); if (exepath == String.Empty) { Console.WriteLine("[WARNING] Please install Turtoise SVN with command line client option!"); } else { Console.WriteLine("[INFO] Turtoise SVN detected. \r\n\tPath is: " + exepath); exepath = String.Empty; } /// add libdoc.exe to path to enable CODESYS libdocscripting (TODO expand this section) exepath = Helper.FindExePath("libdoc.exe"); string strPath = System.Environment.GetEnvironmentVariable("Path", EnvironmentVariableTarget.Machine); string path = String.Empty; string strNewSystemPath = String.Empty; if (exepath == String.Empty) { /// add path to: "C:\Program Files\CODESYS 3.5.14.0\CODESYS\DocScripting\3.5.14.0" /// for now quick and dirty => should become dynamic path = "C:\\Program Files\\CODESYS 3.5.14.0\\CODESYS\\DocScripting\\3.5.14.0"; strNewSystemPath = strPath + ";" + path; System.Environment.SetEnvironmentVariable("Path", strNewSystemPath, EnvironmentVariableTarget.Machine); Console.WriteLine("[INFO] Environmentvariable for DocScripting added: \r\n\tPath is: " + path); } else { Console.WriteLine("[INFO] DocScripting detected. \r\n\tPath is: " + exepath); exepath = String.Empty; } } /// <summary> /// Expands environment variables and, if unqualified, locates the exe in the working directory /// or the evironment's path. /// </summary> /// <param name="exe">The name of the executable file</param> /// <returns>The fully-qualified path to the file</returns> /// <exception cref="System.IO.FileNotFoundException">Raised when the exe was not found</exception> public static string FindExePath(string exe) { exe = Environment.ExpandEnvironmentVariables(exe); if (!File.Exists(exe)) { if (Path.GetDirectoryName(exe) == String.Empty) { foreach (string test in (Environment.GetEnvironmentVariable("PATH") ?? "").Split(';')) { string path = test.Trim(); if (!String.IsNullOrEmpty(path) && File.Exists(path = Path.Combine(path, exe))) return Path.GetFullPath(path); } } return String.Empty; /// throw new FileNotFoundException(new FileNotFoundException().Message, exe); } return Path.GetFullPath(exe); } #endregion False False 3
Last updated: 2019-12-03

Ticket #10: attachments to ticket 9 ^{CODESYS Forge tickets (Ticket)}
attachments to ticket #9attachments to ticket 9 CODESYS Forge 0 tickets Ticket tickets attachments to ticket 9 2019-12-03 15:52:58.656000 closed False 0 aliazzz Ticket #10: attachments to ticket 9 0 1.0 False /tol/cforge/tickets/10/ None 2019-01-05 17:13:47.024000 None 10 9 cforge attachments to ticket #9 False False 2
Last updated: 2019-12-03

Sort by relevance or date