First of all, Thanks for your answer. I know it, but the problem is that I have more than one deployable in an application, sometimes the new builds has no need to re-build all of them, but in the last step of my deploy plan, I need to update a sql table with the versions of all the deployables included into the build deployed. For that reason I need to access an specific deployable, and then, of course, I will use the $referencedBuildNumber function. "$ReferencedBuildNumber : Returns the build number referenced by the imported deployable in the current scope." Thanks

I think this was a regression 3.8.6; if you upgrade to the latest, you should be able to remove them.

The tutorial still needs to be updated (we will do this for v5), but take a look at the SDK Documentation for how the variable base classes work now; basically you declare them as properties and then use attributes to indicate that they are parameters.

You might be getting that message if you have Windows Integrated AUthentication enabled; this is unfortunately not supported in the npm client. Otherwise if you follow the steps in the npm tutorial it should work just fine.

Thanks, Tod, but I want to keep all the actions on the client side. I found that I can just do a GET and a PUT, and once I constructed the multi-part form data correctly and added a boundary to the content, it worked.

Actually, reading your last sentence again, it sounds like I shouldn't use API keys in cases where I want to keep a feed secure. This is probably the best answer correct? Yes, pretty much. I suppose you could think of it as two different sets of doors that could secure a feed --- the first door (LDAP) is quite secure and can be user/group controlled, whereas the second door (API Key) is quite weak and works a bit like a skeleton key that everyone shares. There's zero point in requiring users to unlock two different doors, which is why we say using an API key doesn't make sense when you've enabled LDAP. If you want to use only an API key, then you must bypass the first door by allowing anonymous. This is less secure and generally not recommended.

This would require creating an after-push adapter using the sdk. Several folks have done this in their own instances, but we currently don't hav ea tutorial for how exactly to write one;, but the classes should be fairly self-explanatory to assist with this.

Thanks, I was able to download the Oracle extension and modify it to look for a custom statement delimiter for testing purposes. A few tests seem to check out fine so I'm able to deploy package updates this way. This means I have to customize my deploy scripts but this may be an acceptable tradeoff for now. I've made my statement separator tokens comment sequences (i.e. "--$$") so that the script can still run in sql*plus.

See: http://inedo.com/support/questions/4487

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.

Connectors can only be filtered by ID, so you'll have to rely on the client to filter by pre-release versions. You can clear the cache on the Manage Feed page.

Well, strictly speaking, it doesn't work as advertised, because I was missing the $format. This gives the desired result. http://progetna11.atlas.cm.com/nuget/branch/Packages()?$format=json&$filter=Id eq 'Web'

Hi, upack is the command line client for ProGet universal feeds. We will soon have it available to download from Chocolatey and Inedo.com, but for now you can find it directly at this URL: http://cdn.inedo.com/downloads/proget/upack1.0.0.zip

I'm afraid we don't have that tutorial yet; but we'd like to soon!

hi, i think this is not an nuget or chocolatey specific thing. proget has to render the *.nuspec infos. like uget gallery https://github.com/NuGet/NuGetGallery/issues/2280 regards sundayout

Not currently, it's just per application level right now. We will definitely consider adding that in a 5.x release!

Thanks. Once I gave the anonymous user delete package privileges, and passed the API key as a header, I was able to accomplish this. However, I find it odd that a successful DELETE call returns nothing.

ProGet is the server, so it just hosts your private packages. If you want to push something to a different feed, use the -Source ... argument in the nuget.exe client. Connectors for NuGet are simply a convenience that make it easy to cache nuget.org packages and provide a single endpoint to download them.

Ya thats goes well! thanks alot. Its working now.

There currently is no transform for this and it's unlikely we will add one.