Push latest AppDep package to Nuget feedback about corert HOT 9 CLOSED

@gkhanna79, I physically uploaded the package and saw contents, the folder is present. Could you check if it made it?

from corert.

@schellap - I have confirmed by running the build and also explicitly executing the commands in runtest.cmd that the package without CPPSDK folder is being restored. Also, I am unable to access your feed URL after logging into myget.org.

Can you please check what is restored for you and what is present in the feed if you explicitly download the package and rename it to zip to examine its contents? Since the updated package also had version "1.0.0-prerelease", I wonder if myget is not performing the update at all. In that case, can you please delete the old package and push the new one? Otherwise, we can try updating the version as the last resort.

from corert.

Gaurav, I just downloaded at home from the feed and it contains the CPPSDK folder. I've granted you privileges to access/modify the feed/packages. Let me know if you still don't see it and I will delete and recreate.

from corert.

I issued, and I saw

cd tests
..\packages\NuGet.exe install -Source https://www.myget.org/F/schellap/auth/3e4f1dbe-f43a-45a8-b029-3ad4d25605ac/api/v2 -OutputDir . -Version 1.0.0-prerelease Microsoft.DotNet.AppDep -prerelease
dir
cd Microsoft.DotNet.AppDep.1.0.0-prerelease\CPPSdk

I was able to get there. May be there is a HTTP cache that you need to clear from IE?

from corert.

Actually, I checked immediately after uploading early afternoon by downloading it, it was present.

from corert.

Need to specify --Nocache to nuget install to force it to download the package.

from corert.

Need to specify --Nocache to nuget install to force it to download the package.

We should be pushing package updates with new version numbers so that this is not necessary. The '--nocache' flag makes you hit the network every time. It is slow and otherwise not a good idea because you need to have good network connectivity to do any work now.

Also, replacing packages inplace tends to breaks folks who are still on the old version of the package.

from corert.

+1 pushing things with the same version is a nuget no no

from corert.

Yes, that is the plan as we update the packages in future. I just called out that this is how I fixed the issue for my machine that had the problem.

from corert.