create-package | Ultimate starter kit for JS , JSX , TS , TSX modules | Frontend Framework library

I have defined and created a content-only package to share JSON schemas between different projects. I packaged it using nuget.exe, and could successfully add it to .Net Framework 4.6 library project.

But when I tried to add it to the DotNet Core 3.1 library project (NUnit tests) the following error occurred:

I'm creating a nuget package that is refercing a number of different packages for the platforms.

I don't sem to be able to reference Xam.Forms.Platform. from the various ItemGroups as well as packages I've added via nuget for specific platforms.

I'm using this as a reference : https://docs.microsoft.com/en-us/nuget/guides/create-packages-for-xamarin and my csproj is this

I use Poetry to build tar.gz. and .whl of my package. Cython docs recommend to distribute cython generated c files along with pyx ones. http://docs.cython.org/en/latest/src/userguide/source_files_and_compilation.html#distributing-cython-modules

What should I add to build.py or pyproject.toml to generate c/cpp files by calling poetry build and poetry build -f sdist?

I tried this (from Create package with cython so users can install it without having cython already installed):

build.py:

I am trying to run packagedeployer using PowerApps Deploy Package and getting an error "You cannot call a method on a null-valued expression". This is a CRM Package solution that is created using Dynamics 365 SDK templates. Please find below the link with details

https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/package-deployer/create-packages-package-deployer#create-a-package

Azure DevOps Error Screenshot

Having a problem publishing a package with only build utilities. Being precise: I followed the nuget guideline which files have to be where. So I created a simple [project][2] in which I just want deploy the .props and .targets files in the build folder for third-party projects. When I pack it with dotnet pack Teronis.Packaging.ProjectBuildInPackage.csproj --configuration Release) the .nupkg file does contain all necessary files:

I am working on creating a sample Nuget package to test out the process of creating an internal Nuget package for use in another project of mine. My end goal is to create a simple Nuget package, which can be installed onto another simple C# project, and tested out.

I have been following the Microsoft tutorial to create & publish a package using VS: https://docs.microsoft.com/en-us/nuget/quickstart/create-and-publish-a-package-using-visual-studio-net-framework

I successfully created & published my package on nuget.org, called MyNugetPackage, and attempted to install it onto my other C# project called TestingMyNugetPackage. I received an error in the NuGet package console stating:

Package does not support any target framework

This error makes sense, because I had read about supporting multiple .NET versions and specifying the version under the lib folder, and I definitely did not do that when creating my package: https://docs.microsoft.com/en-us/nuget/create-packages/supporting-multiple-target-frameworks

This idea of lib folder makes sense to me and I think I understand how to add my target .NET version to it. However, I cannot find this folder anywhere! It's not anywhere in the C# project directory. I assume I may need to create it on my own, but I'm not sure where to put it.

Many tutorials and SO questions I have read about this topic talk about how to use the lib folder, but no one ever says where it is. I'm a complete beginner to this and I know I am missing something obvious here, but I'm not sure what it is.

Edit: I did try to change my .nupkg file to a .zip file and extracting the contents in attempt to view the lib folder. This did work in extracting the contents, but I did not see any lib folder after expanding entire project tree and searching for lib.

Here is a quick layout of my C# solution tree:

Solution titled MyNugetPackage with a MyNugetPackage.sln file, a MyNugetPackage.csproj file, and a simple class Logger.cs that just has a public void Print(string text) { Console.WriteLine(text); } method:

I have a two-part project. Part one is a set of C# bindings that wrap a native .dll or .so library. This produces a NugGet package, which is then consumed by the other project.

The other is a Xamarin Forms project that consumes those C# bindings. The UWP portion of my Xamarin project has no issue finding the native library inside the NuGet package. The Android project, however, cannot find it. Indeed, opening the APK reveals that the native .so file never makes it in.

I'm using NuGet's mechanism for including arch-specific libraries, by including each platform-specific .dll-or-.so in a /runtimes/platform-arch/native/ folder. My folder structure looks like this for the bindings project:

...and I can confirm that the folder structure is properly preserved in the resulting .nupkg file, with a runtimes folder at the root of the package, and a series of subfolders underneath it.

I generate the NuGet package by using the new built in .csproj mechanisms, without any .targets files. My csproj for the NuGet project looks like this:

I have a C++/CLI DLL that interfaces a third party native DLL. I want to pack this as Nuget.

I followed this official MS guide, this blog post and read through this other question.

So here is what I did:

First, I created the proper nuspec file:

I'm busy adding support for multiple .net frameworks and platforms. The different frameworks seem to work. But if the right platform specific dll is used I don't really know how to check this. Now it seems that the MSIL/Any CPU version is always used...

First the nuget package

I followed the descriptions at:

https://docs.microsoft.com/en-us/nuget/create-packages/supporting-multiple-target-frameworks

And I'm also using .targets and .props files.

For the code look at Pullrequest Opensource project: https://github.com/lucascebertin/Serilog.Sinks.Burst/pull/1

Using the nuget package

When using the Nuget package everything seems to work. But currently I do 2 checks to see if the right platform dll is used. Note: The platform choice is MSIL/Any CPU, x86, and x64.

I do a diff between the dll in my package and the extracted/copyied one in the bin folder of the using project: Looks like the MSIL/Any CPU dll version is copyied.

The second check is from code to see which dll is used runtime: