Yes, that would do it; the $WorkingDirectory() function will always ends return a slash. So, you'll want to definitely trim it; you can do this with a $PSEval, but we will have built-ins soon - https://github.com/Inedo/inedox-inedocore/issues/9

In v5.4, we will have a "Custom Setter" for template variables which would allow for this scenario. Our primary use case is to allow for a searchable list of packages from ProGet, or builds from teamCity/Jenkins/etc to be populated.

David, great to hear! Aris, would you mind opening a new thread, or submitting a ticket (maybe easier to back and forth on email); I think I understand what you're suggesting. We'll definitely have to re-engineer something to support this sort of usecase, so any more details on how it should behave (from the UI, pipeline JSON, etc) would be helpful!

This isn't currently supported, but we can add an endpoint for that. Sounds like it would fit in the Package Deployment API (see roadmap). Of course, we can always ship these in earlier maintence releases, they just won't be documented and may change before final releases.

Thanks; I can see the issue, it appears if the environment is the same, then this may occur, depending on which one fails first. We will investigate.

Please ignore this question. It works now.

Great! Thank you for the quick response, and also for an excellent lead time. Impressive!

Hi Dean, thanks for your reply. Redownloading the installer has resolved the issue. Best Regards Alex

Here is an example path to a .pdb file, the same folder contains .dll: C:\Users\nsitnikov.dnx\packages\JA.AppCentral.Logging\0.1.7-Build1\lib\dnx451\JA.AppCentral.Logging.pdb Package folder also contains the source in C:\Users\nsitnikov.dnx\packages\JA.AppCentral.Logging\0.1.7-Build1\src folder

Thanks for the quick response. Yes, sooner would be great. I will start using the new feature as soon as you can release it, with or without documentation.

If I use this string it returns me: System.ArgumentException: 'server' is not a connection attribute valid. What should I use instead?

Check out KB#1039 - The Inedo Agent and Legacy BuildMaster Agents for more information on this.

That's generally the idea of the arguments: those are the required variables. template MyTemplate<$var1,$var2,$var3> { ... } It's generally a good practice to use these instead of external or configuration variables. But you can always use the $IsVariableDefined function as well. if !$IsVariableDefined(my_var_name) { error; }

ignore my previous post. I had modified a second action and had left the first one with spaces, the semi-colons worked fine. Thanks

Just a heads up, that we've updated the docs with our proposed specifications, always open to feedback! Formal Grammar Formal Specification Strings and Literals We don't have an ETA; the changes aren't really that difficult, but once we implement them we're stuck with them.

A FileSystemWatcher is used, so any changes to the directory will trigger an import.

Yes I do see it there. I think the message on the key generation page implies that the key should be visible immediately after generating the key and is perhaps misleading. Thanks for the info.

You are not going wrong :) Support for XSL as the template and data as the instance will be added in v5.3.4 as a separate template type so it doesn't break existing deployments. We'll release this within the next day or so.

That was it. The user had access, but not permission to change schema. I really think this should be catch and a nicer message displayed instead of the installer just crashing though.

Hi Junaid, This is a known issue with npm; basically it's sending a JSON document with two "dist" properties. For example... { "dist": "value1", ..., "dist": "value2" } The JSON Library we're using isn't too keen on that, and we already have a fixe (PG-603) planned/scheduled for the next release.