Support Q & A

Tag Filter: Filter
Viewing Page 1 of 38 (20 questions out of 743)

Private Feed + Public Feed?

3
replies

I want to create both a Public-access feed (meaning anyone can view/download packages, but NOT push), and a Private (Nuget) feed (meaning only authenticated users can view/push). How would I do this? I don't see any documentation for this.

Can this be done using the free version of ProGet, or is that restricted to Enterprise?

Product: ProGet
Version: 3.1.0

HTML in HTTP POST action form parameter?

1
replies

How do I properly encode or escape HTML for a parameter value of an HTTP 'Post to URL' deployment action?

Product: BuildMaster
Version: 4.5.7

Pushing symbols.nupkg - NuGet

2
replies

Hi,

We are currently using ProGet 3.4.6 (build6), and currently I'm trying to push a package along with *.symbols.nupkg, however I'm failing to push the *.symbols.nupkg.

When I try to push symbols package (*.symbols.nupkg), I tried using the following after submitting the *.nupkg, however its not working:

nuget push SamplePackage.1.1.0.symbols.nupkg <api-key> -Source https://proget-srv/symbols/site.team

I'm not too sure with the URL whether its correctly, I assumed its something like e.g. https://proget-srv/symbols/site.team, based on http://inedo.com/support/documentation/proget/feeds/symbol-and-source-server.

Also in http://inedo.com/support/tutorials/debug-into-internal-nuget-packages-with-proget there's a tutorial which shows the endpoint name clearly, however it seems to be an old version and in the new version the URL is not shown anywhere (or at least the administrator can't find it).

However for the *.nupkg its working fine by using something like the following:

nuget push SamplePackage.1.1.0.nupkg <api-key> -Source https://proget-srv/nuget/site.team

Any help will be greatly appreciated it, thanks.

Product: ProGet
Version: 3.4.6

Running ProGet at different base url

2
replies

Hi I want to make proget available at for example

https://dev.mydomain.com/proget/

Is this possible? It seems that it is impossible to make proget think it's anywhere except the root.

https://proget.mydomain.com is not ideal sadly

Product: ProGet
Version: 3.4.5

Source stepping not working

2
replies

I’m just looking at ProGet free version at the moment to see if could be of use to me. I’ve installed it on my local machine using the built-in web server, and can successfully use it as a nuget server, can upload packages and add references to them in Visual Studio, but the thing I can’t get to work is debugging using the symbol server.

The package I have uploaded has the .pdb and source files in it (I use the –symbols flag when creating the package). The ProGet site for the package shows debug symbols are available and indexed.

I’ve set up VS (2013) to pull down the symbols from the feed and have the debugging settings set correctly I believe (Enable Just My Code is unchecked, Enable source server support is checked).

When I debug, the .pdb gets pulled down but the source code doesn’t, so I get an error in the output window indicating that the source file can’t be found.

Can you give me any ideas on how I can get source code debugging to work please?

Thanks in advance.

Product: ProGet
Version: 3.4.5

Duplicating an application and linking only global deployment plans

2
replies

We are currently setting up BuildMaster to work through our build and deployment process. For the most part this is working fine. Because we will be building several internal libraries and applications through BuildMaster, it would be in our best interest to reduce the time taken to spawn up and configure each new application however.

The deployment plans that have been configured largely contain common steps due to heavy use of Release Variables with default values.

Ideally it would be nice if we could create a global workflow which had all but one environment using a global deployment plan. This would allow us to re-use the same workflow but still have the power to tweak the single custom plan as each application requires.

Because it doesn't appear to be possible to have a custom 'per application' deployment plan inside a global workflow (makes sense as the whole thing should be global), we need to look at an alternative.

I've created a sample application which I intend other developers to be able to duplicate as required for each new library or application that needs to be set up. I was hoping that we could just duplicate this through the New Application wizard and it would be able to:

1) Create a new application specific workflow.

2) Copy the custom application specific deployment plan and place a new un-linked instance inside the new workflow.

3) Maintain the global deployment plans so that they still link to the global versions.

Unfortunately it looks like we only have three options at this point in time, and none really fit what I want:

1) Copy Deployment Plans (creates a new instance of each deployment plan, including globals).

2) Link Entire Deployment Plans (exactly what it says on the tin, any change in the custom plan affects the sample application as well as each linked application)

3) Link Only Action Groups (same as 1 but action groups inside the plans remain linked together).

Is there a better way than this?

  • Duplicating with the 'Link Entire Deployment Plans' option.
  • Exporting the single custom deployment plan to XML.
  • Creating a new deployment plan to replace the custom linked one.
  • Re-importing the custom deployment plan from XML.
  • Setting the execution server on all the action groups as it has disappeared.

Product: BuildMaster
Version: 4.6.0

Are there any logs for deleting a package from a feed?

1
replies

I am wondering if there is any log currently being kept for a feed which would show who and when a package was deleted from a feed?

Product: ProGet
Version: 3.4.3

Symbol Source failure

1
replies

A symbol package for a .NET 4.5.2 component is built on TFS and uploaded to a Proget feed. Using Visual Studio 2013, I create a new solution for a console executable and add a reference to this package; I add a line of code with a breakpoint so I can test stepping into the component; I hit debug; It downloads the PDB file correctly to the symbol cache; Visual Studio prompts me to find the source code. It asks for the full path that was used when the package was built on the TFS server. But I don't have the source code on my laptop. I wanted to pull it from the Proget symbol server!

I checked the downloaded PDB with srctool -r. It lists all source files, using the path used on the build server.

Isn't Proget supposed to reindex the PDB file to tell it to obtain sources from the source server? That doesn't seem to be happening.

Can someone help me with this?

Product: ProGet
Version: 3.4.4

No NuGet packages despite setting drop folder

3
replies

How do I get the feed to pick up the NuGet packages in the drop folder? I have configured the path, which is the folder in which we have been serving the packages from (just served as a folder share), but the feed shows nothing and appears to be ignoring these packages. How do I trigger the import process, or what am I missing?

Thanks, James

Product: ProGet
Version: 3.4.5

Composer/Packagist feeds

1
replies

As our company works on PHP/Magento projects almost as often as .NET projects, it'd be quite useful if we could use ProGet to host our own internal Packagist feeds for PHP Composer. We would appreciate it if we could know if Composer/Packagist is currently planned as one of the future registries/repositories for ProGet, and if so, by which version is it planned to be supported.

Product: ProGet
Version: 3.4.5

Support multilingual

1
replies

Since we’re a Quebec based company, we’re forced by law to enforce French language in our applications so it would be really great if the admin site would be Multilingual.

Is there a way to translate it using ressource files?

If you provide us with these files we can translate it.

Regards

Product: ProGet
Version: 3.4.2

Support Ie 8.0 in browse package

1
replies

The browse package doesn’t work well in IE 8

Image Text

Image Text

Image Text

Product: ProGet
Version: 3.4.2

Implementing IClientCommandProvider.GetClientCommandPreview

3
replies

 

// Summary:
//     Returns a string containing the command to be passed to the tool.
//
// Returns:
//     String containing the command to be passed to the tool.
//
// Remarks:
//     This will typically be displayed to the user, so passwords should be obscured.
string GetClientCommandPreview();

I'm not sure how to implement this method in any provider without the arguments (string commandName, string arguments) which are provided to ExecuteClientCommand. Has this method been implemented in any of the existing source control providers yet? Right now it seems like a placeholder in the API for something they plan to implement later.

Product: BuildMaster
Version: 4.5.7

Package Error

1
replies

Logged 1/15/2015 10:46:38 AM

Message Error installing package: The package Test.Test.Constants.1.2.2.0 already exists and the current user or service does not have the Feeds_OverwritePackage privilege.

Stack Trace at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo) at System.Environment.get_StackTrace() at Inedo.ProGet.Diagnostics.DatabaseErrorMessenger.Inedo.Diagnostics.IMessenger.Message(IMessage message) at Inedo.Diagnostics.Logger.Message(MessageLevel messageLevel, String message) at Inedo.ProGet.Service.DropPathMonitorExecuter.Execute() at Inedo.TimedExecuterBase.ExecuteMethodHost(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.TimerQueueTimer.CallCallback() at System.Threading.TimerQueueTimer.Fire() at System.Threading.TimerQueue.FireNextTimers()

all users have Feeds_OverwritePackage privilege

Product: ProGet
Version: 3.4.2

Admin_ManageFeeds doesn't enable access to Configuration/ManageFeeds pages

1
replies

We've created a role to give our software engineers control of a feed they are going to own and control the Connector Filter. We've given the role Admin_ManageFeeds but that doesn't enable the gear icon to config and the get errors when trying to access the config or managefeed pages. The can access the "administration/feeds/edit-feed?feedId=2" directly if I give them the URL to their particular feed.

Product: ProGet
Version: 3.4.1

No latest packages

1
replies

In older versions of ProGet there was a list of the latest uploaded packages on the start page. In this new version that seems to be gone. Is there any way to get it back?

Product: ProGet
Version: 3.4.1

Delay before package download starts

5
replies

We are using Proget in LoadBalancingMode (2 web servers, 1 app server, 1 DB server with packages on a shared SAN) and have just upgraded to 3.4.1.

We have a feed of 21,000 packages (~5GB) with no connectors, no filters and no adapters. Browsing around the feed is very quick but when we try to download a package there is a delay of around 15s before the download starts which is then very quick as the packages are around 100k.

We've created a second feed with just half a dozen packages in and this does not have the delay so it certainly seems to be a product of the size of the feed.

First question is this normal for a feed of this size? Should we be looking to reduce the size? If it is doable is there any logging we can enable or techniques we can employ to try and understand where the delay is? We're currently using Wireshark to look at network traffic (traffic to the package folder occurs just before the download starts) and SQL profiler to look at the database (no obvious delays here).

We get the same behaviour with both built-in and integrated authentication.

Thanks in advance.

Paul

Product: ProGet
Version: 3.4.1

404 when browsing to npm URL

4
replies

We are evaluating your product for a private repository of NuGet and NPM feeds. When creating a new NPM feed, the URL that is presented to the user does not work and produces a 404.

  1. Installed ProGet on Windows 7 machine with IIS and SQL server
  2. Configured Windows Integrated Authentication
  3. Verified that NuGet functionality works fine
  4. Create a new NPM feed called "test-npm-feed"
  5. Pulled a package from an external registry (ex "browserify 8.0.3")
  6. Opened the NPM package in ProGet
  7. Clicked on the "configuring npm" link
  8. Attempted to browse to the following link and received 404

npm config set registry http://my_machine_name:81/npm/test-npm-feed

Product: ProGet
Version: 3.4.0

Filtering Feed Browser

2
replies

Is it possible to filter the feed browser for a feed that also has a connector?

i.e for a feed that has a connector to, say, NuGet.Org, but also has locally stored packages it would be great to see, say, only the locally stored packages.

Product: ProGet
Version: 3.4.1

No Bulk Import Option?

2
replies

I'm looking to move an existing "Legacy" Feed as detailed in this KB article: http://inedo.com/support/kb/1092/migrating-legacy-proget-feeds

However, when I create the new feed, there is no option on the NuGet Feed type to specify the Bulk Import Location ?

Product: ProGet
Version: 3.4.0

Page: 134567891011121314151617181920212223242526272829303132333435363738