Hi @easonyang
Can you try againg ? This was caused by a rule on on firewall. It should be working now.
Thanks,
Hi @easonyang
dotnet restore before the build operation ?Thanks,
Hi @MichelZ
Do you still have problem. I'm sorry that I missed your reply. We have made some improvements on our website about this problem.
Thanks,
Hi @dmeagor
Yes, we removed some packages which shouln't be on our NuGet server but on nuget.org. Please let me know if you face any problems.
Hi @dmeagor
Could you try again ? This should be fixed now.
Thanks,
Hi @MichelZ
I'm not %100 sure but your requests might be blocked by our firewall. Is it possible to share your IP with us so we can check this ? You can share it with info@abp.io.
Also, using a nuget cache for your docker builds might help to solve this problem and speed up your development, see https://stackoverflow.com/questions/60799918/using-nuget-cache-inside-a-docker-build-with-net-core-when-offline.
Hi @selinkoykiran
You were right, the prerelase filter is not used at all when searching the packages. We have fixed this problem. The fix will be published soon.
Hi @beuko
This is a different problem. Could you create a new 4.4.1 project, it should be working fine now.
Thanks,
Hi @selinkoykiran
Are you using a 3rd party library ? If so, can you share it with me ?
Thanks,
Hi @selinkoykiran
I tried with VS 2019 and it worked as expected for me. When I check the package status, it is correctly marked as a PreRelease package. Sometimes Visual Studio cna mix the requests for getting the package information from the package source. Could you wait for a few seconds when you click the PreRelease checkbox and see if it makes any difference ?
By the way, does this cause any problem on your CI/CD pipeline ?
Hi @MichelZ
Yes, the release of 4.4.1 is still in progress, could you try again when the release is completed. We hope to complete it today.
Thanks,