I forked your repo and created both packages, however both packages can display well on my VS2019 without ‘prelease’ checked, could you please have a double check? eg, recreate package and change another vs client?

@weide-zhou thanks to try and let me know, I’ll double check, but I already created a new version of the package several times. 

About change another VS client, do you mean a different Visual Studio/PC? not the one I’m using?

thanks

I can confirm that on my friends VS worked, thanks :slight_smile:

So what is the solution now? I have the same problem all my packages are only available for installation if pre-release checkbox is ticked.

I’m getting the same thing. Publishing *Private* packages to a private repo and they only show up if you click the Prerelease checkbox. Glad I found your post as I thought I was going mad.

As above mentioned this is not working for me.  Packages show as prerelease.  When are we going to see UI to manage packages.  GraphQL is not a solution calling raw APIs.

Did anyone has a solution? 

There’s some minimal properties that you must specify inside the PropertyGroup tag on your csproj.

<PackageId>AppLogger</PackageId>
<Version>1.0.0</Version>
<Authors>your_name</Authors>
<Company>your_company</Company>

In my case I was missing an explicit Version tag even though I was generating one when doing dotnet pack.

@robturnerovo wrote:

There’s some minimal properties that you must specify inside the PropertyGroup tag on your csproj.

AppLogger
1.0.0
your_name
your_company

In my case I was missing an explicit Version tag even though I was generating one when doing dotnet pack.

I’ll try this solution out, but both of them are without these properties, first one works and second one no