Building a cloud service, and using a MSFT hosted build controller. And would like to use nugetter build templates to build and publish NuGet package.

Is this possible?

Followed the default Simple project example in the nugetter documentation.

Right now my drop location which is in our TFS is giving a UnauthorizedAccessException.

Exception Message: Access to the path **** is denied. (type UnauthorizedAccessException)

Triscuit,

So the NuGetter assembly installed where the controller can find it?  If so, at what point is the access denial happening?  In other words, is there other information in the build log to indicate at what point the error happens?

Mark

Hey Mark,

Thanks for your response.

1. I'm using the NuGetterStandardBuildTemplate.11.xaml and that points to a location in our TFS with the NuGet.Exe (it gave an error of not finding the .exe before and that has been fixed, so I'm pretty sure it knows where the .exe is).

2. The build only gave a stack trace and no log file (I have the regular build log file but there are no errors associated with that).

*** replaces drop folder used by the build template.  

Exception Message: Access to the path '$/***/***/***/***\NuGetPackage' is denied. (type UnauthorizedAccessException)Exception Stack Trace:    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)   at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)   at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)   at TfsBuild.NuGetter.Activities.CreateFolder.Execute(CodeActivityContext context) in c:\Users\svc-tauintbuilder\Downloads\Source\TfsBuild.NuGetter.Activities\CreateFolder.cs:line 53   at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)   at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

One weird thing I notice is the path uses a '\' right before the Output directory compared to using '/' elsewhere in the path.

Another thing to note is that the NuGet.exe being used is a custom built solution to support VS2012 and not the public Nugetter package.

In the output directory field, I left that as default (NuGetPackage), so there's no source control stuff there.

On the "build defaults" page the staging location points to a source control location, with the "Copy build output to the following Source Control folder."

So that's where I believe that's where the source control path is getting in from.

You're saying that this will need to build at a UNC path instead of a source control location?  This would be difficult on a hosted built controller.

Ok, I understand now.

That is a problem since the packaging process happens after the build and is expecting that it is working on a disk.  It's not that a UNC path is needed specifically - just a disk to continue working on the build output. It currently works where the drop location is specified.  Even on a hosted platform the build can't be working solely on files in source control.  It must be working on disk and then copying the files to source control.  The trick is figuring out where during the build.  Now that I get what is happening I can attempt to reproduce the problem although I can't give exact specifics on if/when I will be able to add the capability of working in a hosted environment.

Mark

Hey this is awesome.

Thanks so much for your help.

The other solution I looked into was getting a build controller spec'ed out with all the necessary NuGet and Azure stuff.

But it so much easier using a hosted build controller :).

This is going to be harder than I thought.  In VS2012 you can't see the "Copy build output to the following Source Control folder:" option.  In VS2010 you can see it however you can't use it.  Apparently, it is really only an option in a hosted environment so I won't be able to reproduce the situation in a controlled environment. Uggh.