Support Q & A Home

Ask A Question

Anyone can ask or answer a question here, but our support engineers actively monitor your questions; we typically answer within a day or two.

Filter
Viewing Page 69 of 105 (20 questions out of 2087)
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

5
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

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

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

1
replies

Is there a plan to support a NPM feed with Windows Authentication enabled?

Product: ProGet
Version: 3.4.0

1
replies

Does ProGet have logging beyond errors? I am looking to see if it has standard security logging like user actions (login/logout, success/fail), administrative actions (add/remove users, group modifications, feed modifications, etc.).

Product: ProGet
Version: 3.4.0

14
replies

I have one particular feed on my ProGet instance that results in a very lengthy pause before downloading items, to the point of being unable to install packages within Visual Studio.

The feed is the new index format (v3.3+) and fiddler logs tell me that other feeds return fine.

GET /nuget/MyFeed1/FindPackagesById()?id='Apache.NMS.ActiveMQ' HTTP/1.1
DataServiceVersion: 1.0;NetFx
MaxDataServiceVersion: 2.0;NetFx
User-Agent: NuGet VS Packages Dialog/2.8.50926.663 (Microsoft Windows NT 6.1.7601 Service Pack 1, VS Professional/12.0)
NuGet-ProjectGuids: {FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}
Accept: application/atom+xml,application/xml
Accept-Charset: UTF-8
Host: starlizard-nuget:8081
Accept-Encoding: gzip, deflate

After 30 seconds delay...

HTTP/1.1 500 Internal Server Error
Cache-Control: private
Content-Length: 35
Content-Type: text/plain; charset=utf-8
Server: Microsoft-HTTPAPI/2.0
X-AspNet-Version: 4.0.30319
X-UA-Compatible: IE=edge
X-ProGet-Version: 3.4.0.7
Date: Mon, 12 Jan 2015 20:08:49 GMT

Occasionally it works but with a very large delay (20+ seconds) - seems as if once it waits for longer than 30 seconds, proget hits a timeout and throws a 500 error.

The feed has approx 3,000 packages but I wouldn't have thought it that's near its maximum?

Cheers,

James

Product: ProGet
Version: 3.4.0

1
replies

Hi,

I have BuildMaster looking at a GIT repository. When I add a new branch, Build Master is not able to see it until I delete the existing repository from where BuildMaster is installed (c:\buildmaster_svctmp\GitRepositories). Once I delete it from there, BuildMaster sees the new branch.

I have tried using the simple Git client and installed an the Git 1.9.5 client. Both have the same problem.

From what I can see, once BuildMaster has downloaded the repository, it does not look to find any new branches created in the repository. Once I delete the repository in BuildMaster, it appears to be fixed as BM has to download the repository again.

Is there something that I have missed with my setup?

Regards,
Pedro

Product: BuildMaster
Version: 4.5.7

1
replies

Can someone point me to documentation or examples of using buildmaster with flashbuilder?

Product: BuildMaster
Version: 4.5.7

3
replies

Is there a way to configure ProGet to cache proxied nuget.org packages the first time it gets installed in my project? I noticed that you have to manually log into ProGet and click the “download” button on a nuget package to actually have it available in the cache. That is not ideal for us.

Product: ProGet
Version: 3.3.12

3
replies

Install on a Win 7 workstation as Windows Service went well. Install on a Windows Server 2012 R2 having problems. Tried as windows service. Had some kind of network or firewall issue. Tried turning firewall off. Tried uninstall and reinstall as web app into IIS and installer seems to ignore that and install the windows service anyway.

Installed as windows service for port 80 (Default site in IIS is changed to port 8088). And I still get "This page cannot be displayed." both from the server console and across the LAN from a client.

Ideas?

Product: ProGet
Version: 3.3.12

1
replies

When the package manager tries to retrieve the packages list, it sends a request to the server :

http://myserver/nuget/myfeed/Packages()/$count?$filter=IsLatestVersion

With the version 3.3.11, the server responds nothing and the package manager displays nothing. With the version 3.2.1, the server responds correctly with the number of packages.

Could you do a patch for this issue ?

Product: ProGet
Version: 3.3.11

1
replies

The ProGet server works for me. I'm working on Windows 2012R2 Server.
First I had the problem that the ProGet service was not recognized running when working with IIS installation (in dedicated Site with dedicated https binding). But the service was running without problems even when i ran the same command on console.
With the currently running embedded installation the service is shown as running.

With both variants I have the following problem:

When I update a package with source the new source won’t show up in Visual Studio.

Say I had the version 1.0.28 of a package with a bug. I fixed the bug in version 1.0.29 but Visual Studio loads the old source from the version 1.0.28.
Even when I remove the symbol caching folder the old source loads and shows up.
Both packages show up in the gallery with “Symbols and source files are available” and when I download the “Package with Symbols” from the gallery link the corrected source is in the downloaded nupkg.

Now when I remove the old package 1.0.28 from the gallery then the source cannot be found anymore from Visual Studio. If I clear out the symbol caching folder the new source is loaded. So why is it necessary to delete the package on gallery and remove the local symbols cache to get the new source? Shouldn't Visual Studio load automatically the source with the corresponding version of the package linked in project?

My Visual Studio Version is Premium 2013 Update 4.
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Version 4.5.50938

NuGet Package Manager 2.8.50926.663

ProGet is 3.3.11

Under “Symbols & Source” on the gallery is a link view which shows up where the pdb is located in the package. At the end of the line is a field named “Age”.
What does this field mean? Is there an indicator for such problems on indexing?
In my sample the version 1.0.28 shows an “Age” of 13 and the new version 1.0.29 shows the “Age” of 14.

I hope you have some suggestions for my problem.

Product: ProGet
Version: 3.3.11

1
replies

In BuildMaster v4.5.7, when I drag and drop action groups in the deployment plan editor, sometimes they do not automatically update the page. If I refresh the page manually, they will end up in the correct spot.

Product: BuildMaster
Version: 4.5.7

3
replies

Hello,

I'm trying to publish to our enterprise's internal proget server. Everything is going correctly in the CLI output (no indication of errors) and I'm set up with appropriate roles/access in the proget web config.

But the new version I'm trying to publish (which is a patch level bump from 8.0.0 -> 8.0.1) isn't showing up in the feed. Here is some output (with obfuscation of the server name):

Attempting to build package from 'Foundation.Web.Content.nuspec'.
Successfully created package 'C:\src\Foundation\Source\Foundation.Examples.UI\Foundation.Web.Content.8.0.1
.nupkg'.
WARNING: No API Key was provided and no API Key could be found for 'http://example:81/nuget/Defau
lt'. To save an API Key for a source use the 'setApiKey' command.
Pushing Foundation.Web.Content 8.0.1 to 'http://example:81/nuget/Default'...
Your package was pushed.
Cleaning up Packages locally
Local Packages Cleaned up
Attempting to build package from 'Foundation.Services.JumpStart.x64.nuspec'.
Successfully created package 'C:\src\Foundation\Source\Foundation.Services.JumpStart.x64\Foundation.Servic
es.JumpStart.x64.8.0.1.nupkg'.
WARNING: No API Key was provided and no API Key could be found for 'http://example:81/nuget/Defau
lt'. To save an API Key for a source use the 'setApiKey' command.
Pushing Foundation.Services.JumpStart.x64 8.0.1 to 'http://example:81/nuget/Default'...
Your package was pushed.
Cleaning up Packages locally
Local Packages Cleaned up
Attempting to build package from 'Foundation.Migrations.Baseline.nuspec'.
Successfully created package 'C:\src\Foundation\Source\Foundation.Migrations\Foundation.Migrations.Baselin
e.8.0.1.nupkg'.
WARNING: No API Key was provided and no API Key could be found for 'http://example:81/nuget/Defau
lt'. To save an API Key for a source use the 'setApiKey' command.
Pushing Foundation.Migrations.Baseline 8.0.1 to 'http://example:81/nuget/Default'...
Your package was pushed.
Cleaning up Packages locally
Local Packages Cleaned up

When I go into the Default feed and look at any of these packages, I don't see the 8.0.1 version at all (only 8.0.0 is shown as the latest). Any help would be greatly appreciated.

Thank you,
Jeff Olson

Product: ProGet
Version: 3.1.7

3
replies

I know the link "http://inedo.com/support/documentation/proget/feeds/api-keys" but this does not tell me how we can assign groups or users to the feed or not.

How can we do that?

Product: ProGet
Version: 3.3.11

1
replies

Tried the following methods and none of them help

C:\sources>nuget push "ThePackage.1.0.0.0.nupkg" -s http://domain.com:81/nuget/FeedName apikey

C:\sources>nuget push "ThePackage.1.0.0.0.nupkg" -s http://domain.com:81/nuget/FeedName

C:\sources>nuget push "ThePackage.1.0.0.0.nupkg" -s http://domain.com:81/nuget/FeedName username:password

Failed to process request. 'There was an error processing the request: Invalid feed name was specified.'.
The remote server returned an error: (400) Bad Request..

Product: ProGet
Version: 3.3.11

4
replies

VS correctly requests and receives the PDB from the symbol server, but the subsequently requests the incorrect source file. Output from pdbstr.exe reveals the issue:

SRCSRV: source files ---------------------------------------

[BaseDirectory]\contracts\exceptionformatter.cs*ExceptionFormatter.cs

[BaseDirectory]\contracts\streamclient.cs*Client.cs ** INCORRECT **

[BaseDirectory]\contracts\properties\resources.designer.cs*Properties/Resources.Designer.cs

[BaseDirectory]\contracts\channelfactoryextensions.cs*ChannelFactoryExtensions.cs

[BaseDirectory]\contracts\client.cs*Client.cs

[BaseDirectory]\contracts\argumentformatter.cs*ArgumentFormatter.cs

SRCSRV: end ------------------------------------------------

Decompiled Inedo.ProGet.WebApplication.SimpleHandlers.SymbolServerHandler @ ProGet.WebApplication. In ProcessRequestInternal there is a loop to match pdb source file paths to nuget package source files using an IndexOf. In my example, IndexOf results in two matches (Client.cs and StreamClient.cs) and then incorrectly writes the first. IndexOf may also be problematic for same-named files in different sub-directories.

Maybe one potential solution is to first establish a common base path, then match on the remaining relative path in the nuget package:

    /// <summary>
    /// Finds the source base path.
    /// </summary>
    /// <param name="sourceFiles">The source file paths in the NuGet package under the 'src' directory.</param>
    /// <param name="referencedSources">The referenced sources obtained from srctool.exe.</param>
    /// <returns>The most common source base path with respect to matching files in the NuGet package.</returns>
    private static string FindSourceBasePath(IEnumerable<string> sourceFiles, IEnumerable<string> referencedSources)
    {
        return referencedSources.Aggregate(
            referencedSources.First(),
            (b, s) =>
            {
                while ((!s.StartsWith(b, StringComparison.OrdinalIgnoreCase) || !sourceFiles.Contains(Path.Combine("src", s.Substring(b.Length)), StringComparer.OrdinalIgnoreCase)) && b.Length > 0)
                {
                    b = b.Substring(0, b.Length - 1);
                }
                return b;
            });
    }

Product: ProGet
Version: 3.3.11

1
replies

Hello,

Just wondering if there was plans to release a version of ProGet (or another product) that would support PyPI, which is the Python equivalent of NuGet.

Regards,

Jonathan

Product: ProGet
Version: 3.3.10

2
replies

I've already report this problem with STRING.FORMAT.JS 1.09

But if the workaround solution you give me was acceptable for STRING.FORMAT.JS which is a content only package, it's not acceptable for libraries packages

Takes for example the package Moq 4.2.1400.0717.

When installed through nuget.org the leading 0 is conserved on all the stack, in particular when creating the folder in the packages directory

however when using proget the leading 0 will be strip which create a folder name without that 0 in the packages directory resulting in a compilation error because the project is no more able to find the lib (for .\packages\Moq.4.2.1400.0717 do not exists)

I've tried some restore operation with proget as source and nuget.org as source, and cleaning all nuget caches between each test (in particular in "%userprofile%\appData\local\nuget\cache")

  • nuget.org always return a package including the leading 0 even if you ask for the version 4.2.1400.717
  • proget always return a package without the leading 0 causing troubles for compilation after restore and causing trouble during first installation because the nuspec inside the package still have the leading 0

I'm waiting for a real support, and rolled back our configuration files to use nuget.org instead of proget for public packages

Product: ProGet
Version: 3.3.10

Ask A Question
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 69 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105