Thanks for the feedback, the thing that caused some confusion is that for uncached packages on our buildagents, we began to get errors about modified nuget packages after enabling the striping of the symbols from the nuget packages
We can't ask all developers to use this feed to get their packages and re-do of all existing code.
So striping is not an option.
We'll continue to work with the full packages always for now.
We have been looking to add symbols to some packages for our nuget feed.
We enabled symbol support for the feed.
We then tried to provide *.snupkg to the drop folder, where they didn't get picked up.
Ok, we then tried to embed the pdb during the build of the package, but then the pdb are always downloaded because they are part of the dll and striping does not remove them from the dll.
We are not sure what striping now exactly entails when you enable it. Do we have to make nuget packages where the pdb are separately stored or something? Is this something we can configure in the buildoptions of the project or do we have to make the package separately.
Any guidance would be appriciated, thanks in advance!
Today I converted my existing nuget feed I made a while ago to support SemVer 2.0.
This feed was setup in an previous version( 4.7.17) and I now upgrade the feed in Proget version 5.1.21. Before I had the same situation, now I find the correct pacakge with the corresponding versions (4.5.1) too.
If you click on manage feed, you should get a question to upgrade the feed ( If you have the rights probably)
Hope this can help!
We have a Proget Server running since version 4.7.14, now 5.1.21.
We have a nuget package with an version that has been pulled on nuget.org:
You can't see it in the list of versions reported by nuget.org itself.
But this version of the package is still being listed in our Proget installation for some reason and without showing the same warning that it has been unlisted on the details page.
I don't have the unlist option availible for an external package it would seem.
How should I try to resolve this? I was thinking of some kind of retention rule, but I'm not sure if this will resolve it.
PS: To try to fix it I also upgraded the nuget feed to support Semver 2.0, but this didn't help either.
Any help would be appriciated.
Product: ProGet
Version: 5.1.21
I just wanted to follow up a bit on what I did to solve this:
After we started to get this problem more often. I investigated my options to move to an other server.
Looking at the advanced options I now changed my frontend to be hosted by IIS instead of self-hosting. Here I have much more control over the request handling. Since I made the move to hosting under IIS, the performance of the website is back to normal.
So maybe it could be usefull to document the impact between self hosting and IIS. Also I literally guessed the folder I needed to host, I couldn't find the documentation on how to do the switch.
The proget windows service now has almost no load, while the worker process in IIS can handle many more requests!
Have a nice day!
Today for the first time we got "Server too busy" three time in one day.
When I look at the server at that time I don't see a server under load...
Enough RAM avaible ( 50% at least)
Enough CPU time availible ( no load seen)
Disk usage is high but we still have at least 20Gb free ( packages use 10Gb)
When does this condition occur and why doesn't it return to normal again after the 'load' has dissappeared?
Any information for handling this would be appraisiated.
We are looking to upgrading our server too in the future, but this doesn't seem to be related to the server hardware itself. It's not under heavy load, unless It something not so obvious.
Product: ProGet
Version: 4.7.14
Thank for the fast response
I have been further investigating the issue and I saw the following result:
Testing against the 'official' v2 api :
PM> find-package swashbuckle.aspnetcore
Id Versions
Swashbuckle.AspNetCore {1.0.0}
Swashbuckle.AspNetCore.SwaggerGen {1.0.0}
Swashbuckle.AspNetCore.Swagger {1.0.0}
Swashbuckle.AspNetCore.SwaggerUi {1.0.0}
Carable.Swashbuckle.AspNetCore.D... {1.0.0}
Swashbuckle.AspNetCore.Examples {2.3.1}
SwashBuckle.AspNetCore.Microsoft... {0.4.0}
When testing 'official' V3 API : same result.
When testing against a proget nuget feed:
PM> find-package swashbuckle.aspnetcore
Id Versions
Swashbuckle.AspNetCore
Swashbuckle.AspNetCore.SwaggerGen
Swashbuckle.AspNetCore.Swagger
Swashbuckle.AspNetCore.SwaggerUi
Carable.Swashbuckle.AspNetCore.D... {1.0.0}
Swashbuckle.AspNetCore.Examples {2.3.1}
SwashBuckle.AspNetCore.Microsoft... {0.4.0}
You see 4 packages are not able to report their version information.
It is strange because the Proget website does show the version information...
For now this is not a blocking issue for me because it is enough to specify a version number and it works!
Hopefully this can be solved, at least you know about it now, :-)
Good day!
Hello,
I started to work in VS2017 and I noticed a strange behavior when trying to add a fairly recent nuget package to my project.
Some background information:
I wanted to add swashbuckly.aspnetcore to my .NET Core 2.0 project.
I use a nuget feed defined in proget to get my packages.
When I start searching in Visual Studio 2017 for this package, I get a search result back without version information and I can't start the install.
When I try to add the package in the package management console ( again pointing to proget Nuget feed) I get a message back, cannot find the package.
But if I specify the version, it does work! So apparent retrieving the version info for this package is problematic?
When I switch to the official feed (nuget.org), I do get the version information and I am also able to install the package without specifying the version
Finally when I go to the web interface of Proget, the package is listed and availibe to install.
I understand that this maybe is not your problem, but I hope to get a clue what the problem is.
I know that Nuget 4.0 is used in Visual Studio 2017 and is it maybe something in the api communication that proget uses that is different from https://api.nuget.org/v3/index.json
Any information you can provide me would be usefull
Product: ProGet
Version: 4.7.14
We would like to host development packages and release candidates on the same feed as our production packages, only problem is that when we update a development build with version 0.0.0 or version 1.0.0 , that version is given when you ask to install the package without version info.
We would expect the highest version released to be picked. Is there something that we do to improve this?
I don't see anything in the recent release notes that would seem to adress this issue.
Can you help with this?
Product: ProGet
Version: 4.4.1
I've have succesfully setup a feed for npm on a server, not my machine.
I can install npm pacakges, but I get errors on some packages, because their dependencies insist on going to the https://registry.npmjs.org/ website. This url is only accessible from the the server where Proget is running, not from my machine.
I've read that some packages include the source from where they want to look for their dependencies and is not overruled apparently by the registry settings set on my machine which point to the proget server installation.
Is there a way to solve this within Proget?
My Example case: npm i angular-cli -g stops on package netw. ( I can install it manually, but not in the flow of depencies of angular-cli.)
I'm currently evaluating the free version with a Nuget feed, npm feed and a bower feed...
Product: ProGet
Version: 4.1.1