![]() ![]() On Windows you may execute: bin/smartsvn.exe -server-mode. This article will show how to use this socket-based command API for custom integrations of SmartSVN.įirst of all, SmartSVN has to be started, either normally or by supplying the -server-mode command line parameter (requires Java 6) which prevents a project window to occur. This is how the Windows Explorer Integration and the Mac OS X Finder Integration are working. While SmartSVN is running, it can receive commands to be executed, like opening a file compare for a versioned file. The start command makes the command line window occur and the pushd seems to be some kind of hack to switch to the directory which is the next parameter. What does the switches and commands mean? The /c switch tells cmd.exe to execute the following command line parameter as command. If, for example, the command would be executed for the path E:\my projects\foo, the second parameter will actually be If the actual directory path contains spaces, we need to surround the placeholder with quotes by specifying double quotes. Because our command contains spaces, we need to wrap it in quotes. Basically, the cmd.exe needs two arguments, /c and the command to execute. in the Command input field specify the path to the cmd.exe, for my Windows XP system C:\Windows\system32\cmd.exe.open the Preferences and select the page to configure the directory command (in SmartSVN it is named Directory Command, in SmartGit Directory Tool).When I right click a directory in our SVN client SmartSVN or Git client SmartGit on Windows - especially the latter, because it does not yet support all Git commands - I want to open a command line shell window.Īlthough it is easy to execute a command with cmd.exe, it seems not that obvious how to open a command line shell window. I had to add a RemoveFile element to the component to ensure that the previously existing file always would be removed before installing the new file: Originally, our WiX-script for one component/file looked like this jar files will be treated by MSI as user data and hence the creation and modification times define whether a file will be overwritten by an update: if the modification time is newer than the creation time, MSI will not overwrite the file when updating. While the Explorer only changes the file’s modification time, Altap Salamander also updates the file’s creation time, an important detail when working with MSI.Īccording to the File Versioning Rules of the MSI SDK, the. But - thanks to the helpful tips in the WiX mailing list - I found out, that Altap Salamander copies files in a different way than the Windows Explorer. Unfortunately, I first could not reproduce the problem, because I used Altap Salamander, a classical two-pane file manager which I can recommend, to copy the files from the intermediate build over the old installation. jar files from the SmartSVN intermediate build over the old SmartSVN installation, before installing the new SmartSVN version. ![]() What has gone wrong? The most important information came from one user who told that he had copied the new. Starting SmartSVN still showed the old version, although the installation process went well without any error message and the “Programs and Features” item of the Windows Control Panel showed the new installed version. Some users reported that installing a new version of our SVN client SmartSVN over a previous version did not work correctly. ![]()
0 Comments
Leave a Reply. |