none
Visual Studio 2017 and Nuget

    Question

  • Hi,

    I can see that it's now easy to crate and publish a Nuget package from inside Visual Studio 2017 but it seems this is only supported for Class Library projects that target .Net Standard.

    Is there not similar support available for Class Libraries targeting .Net Framework too?

    Thanks


    Thursday, April 13, 2017 3:01 PM

All replies

  • Hi Korporal Kernel,

    Thanks for posting here.

    >>>Is there not similar support available for Class Libraries targeting .Net Framework too?

    There is Not similar support available for Class Libraries targeting .Net Framework currently.

    That is because that package references are currently supported for only .NET Core and .NET Standard projects in Visual Studio 2017.

    Package references, using the PackageReference node, allow you to manage NuGet dependencies directly in .NET Core and .NET Standard project files, without needing a separate packages.config or project.json file.

    <ItemGroup>
        <!-- ... -->
        <PackageReference Include="Contoso.Utility.UsefulStuff" Version="3.6.0" />    
        <!-- ... -->
    </ItemGroup>

    Since those NuGet dependencies are managed in the project file, so it's now easy to crate and publish a Nuget package from inside Visual Studio 2017 for .NET Core and .NET Standard.

    Hope this can help you.


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    Friday, April 14, 2017 9:09 AM
  • @Korporal Kernal, any update for this issue? Could get any useful information from the answer? If not, Could please let me know the latest status for this issue? Thanks.


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, April 18, 2017 3:54 AM