I found my mistake I had to specify the "Feed API user" in the API Key configuration.

See: https://stackoverflow.com/questions/45063717

If you are using a newer version of MSBuild, see: http://blog.nuget.org/20170316/NuGet-now-fully-integrated-into-MSBuild.html If you are stuck with an older version, the solution is specific to whatever CI server you're using, e.g. with BuildMaster you would use the NuGet::Install-Packages operation; with TeamCity you would use the NuGet Installer build runner, and so on.

Hello Charles, upack pack expects a directory, not an individual file, so the command should be: upack pack C:\location_of_upack_json_file C:\directory_containing_my_setup_exe --targetDirectory=C:\mytargetDir\build_artifacts

You can Log-Information to see what $WorkingDirectory is. Unless you set a value, it will be something like C:\BuildMaster\_SVCTMP\_Ennn\D0 where nnn is internal identifier of the execution. Log-Information Working-Directory is $WorkingDirectory;

I would suggest to use the "Run MSBuild Script" Action instead. Then you can specify any of the properties.

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

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

If that action is causing issues with that, to get you running again just replace it with a command line action with the same arguments from the BuildMaster log, then add your reference paths that way. As for the actual question, I believe if you specify the same property twice, it concatenates them.

You don't have to install Visual Studio 2015 on the buidlserver. Install MS Build Tools 2015 will do it. https://www.microsoft.com/en-us/download/details.aspx?id=48159

This error is coming from nuget.exe; depending on the version of nuget.exe you're using, AD / integrated authentication simply will not work. It's supposedly fixed in 2.8.2, but some users say it doesn't work in 2.8.3. It's pretty broken in 2.8.1 and 2.8.0. Although it sometimes works in 2.7. The 2.6's seem to be fine, for the most part. ProGet.exe, from the now-defunct client tools, of course will work fine, or a simple HTTP PUT operation.

Hi Tod, Thanks heaps, that makes sense to me. Thanks for the quick reply. Regards, Daniel.

When iam using USB to unlock build master showing error server is not started How can I solve this problem

Ah, thank you so much, don't know how I missed that. :)

You can pull the artifact out of _PublishedWebsites, or try the "This is a Web Application" checkbox. There is a transform config file action available as well, though you can store your configuration files in buildmaster.

Karl, thank you for the quick reply. We have 13 separate projects in just 1 of our solutions, so I was avoiding the tedious job of setting up an action to build each individually. What I ended up doing, and making work, was to just execute mstest.exe on the command line without the /p:OutDir parameter, using an "Execute Command Line" task. Not sure how that will play with the tasks that come after the build, but I suspect as long as I manage my paths correctly in the subsequent actions, it should be OK. Thanks again for the assistance.