search

Dejulia489 / WindowsServiceManager

https://marketplace.visualstudio.com/items?itemName=MDSolutions.WindowsServiceManagerWindowsServiceManager
MIT License
11 stars 9 forks source link

Installation path does not substitute variables #20

Closed dampee closed 4 years ago

dampee commented 5 years ago

If you use a variable in the "installation path", the variable is not substitute with its value.

E.g. I use C:\Services\XYZ-$(Environment.Name)\MyService.exe as the installation path. then the directory "C:\Services\XYZ-$(Environment.Name)" will be created on disk instead of c:\services\XYZ-Test

Dejulia489 commented 5 years ago

I am not familiar with a default environment variable by that name. Are you referencing a custom variable or are you looking for $(Release.EnvironmentName) by chance? If you have a custom variable defined with that name can you please provide your full release log so I can investigate further.

Thanks

dampee commented 5 years ago

The variable is defined here: https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml#deployment-job-variables

Edit: I'll take a look at the Release.EnvironmentName variable. It makes more sense too...

Dejulia489 commented 5 years ago

Ahh the deployment job variables, unfortunately I haven't worked with deployment group variables as much as I would have liked to so I didn't recognize it. Can you please provide your full release log and the Json body of your pipeline.

If there is secretive data please be sure to redact it prior to posting the log.

Dejulia489 commented 5 years ago

@dampee, Is this still an issue?

Dejulia489 commented 4 years ago

Closing for inactivity. Will open if something comes up.