|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Allow environment variables in paths
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Allow environment variables in paths - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Markus Hastreiter Member
|
Hi, it would really be great if you could support environment variables in paths. We're using CruiseControl for continuous integration and we maintain several version branches simultaneously. Right now I have to manually adjust the paths in the sisulizer project file each time we create a new version branch. (just for clarification: the sisulizer project file is of course version specific and resides within each branch). CruiseControl provides some environment variables like "CCNetWorkingDirectory" which we already use in out build scripts (NAnt). So it would be great if I could use these environment variable as the path (or as part of the path) of our (source) binaries. Thanks, Markus
|
||||||||||||||||
| |||||||||||||||||
| Current time is 10:19 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Allow environment variables in paths | |
Sisulizer software localization tool - Three simple steps to localize