Using The NuGet Package Explorer

A NuGet package is a package of source, scripts, binaries, etc., plus metadata for use in Visual Studio.  The best way to think about a NuGet package is to think about it in terms you might already be familiar with: basically a zip or tar ball plus metadata.  The NuGet Package Explorer is a GUI tool which packages source, binaries, scripts, etc., plus metadata into a single file (a package) which is published to a server.  Developers can go to the server and pull your package into their Visual Studio project.

If you are more command-line inclined, then go to this link:
You can download the NuGet Package Explorer GUI and read about it at this link:

The following are some helpful topics for using the NuGet Package Explorer.

To create a package:
1. You will most likely be publishing packages to some internal repository,  http://nuget.internal-url.net, so you can skip Step 2.
2. If you want to publish to the world-wide http://nuget.org repository, create a NuGet account by going here:
3. Use the GUI to build package:
4. When filling out the Package Metadata fields, the Package Explorer will require you to enter certain values, like the Id and Version.  The Id can not contain white space characters, the Version can only contain numbers and periods.
5. Make sure to create a tools folder in your package and add "init.ps1", "install.ps1", and "uninstall.ps1" found here:
6. Make sure you also create a lib folder at the top level, and create two child folders in the lib folder: native and net45.  Make these folders even if they will be empty.  They provide compatibility with .Net.  Like so:
lib\
lib\native
lib\net45 
6. Your project will look something like this:
7. When you save the package locally, the Package Explorer will create a file name that is the Version appended to the end of the Id. For example, if you had an Id of "MyPackage" and a Version of "3.1", the file name created will be MyPackage.3.1.nupkg
8. Publish to:
Url: http://nuget.internal-url.net
Key: SOME-GUID-THING

You must use that key, not the key assigned to your NuGet account if you performed step 2 above.

To delete a package:
Official way:
Private way:
Go to \\internal-packages-url
Just delete your package.

Comments

Post a Comment

Popular posts from this blog

FFMPEG Deinterlacing Modes

FFMPEG has multiple supported deinterlacing filters.  Here they are: 10.14 bwdif Deinterlace the input video ("bwdif" stands for "Bob Weaver Deinterlacing Filter"). Motion adaptive deinterlacing based on yadif with the use of w3fdif and cubic interpolation algorithms. It accepts the following parameters: mode The interlacing mode to adopt. It accepts one of the following values: 0, send_frame Output one frame for each frame. 1, send_field Output one frame for each field. The default value is send_field. parity The picture field parity assumed for the input interlaced video. It accepts one of the following values: 0, tff Assume the top field is first. 1, bff Assume the bottom field is first. -1, auto Enable automatic detection of field parity. The default value is auto. If the interlacing is unknown or the decoder does not export this information, top field first will be assumed. deint Specify which frames to deinterlace. Accept
Read more

Remote debugging with GDB and GDBServer on Alpine and Visual Studio Code

Skip to end of metadata o to start of metadata gdb and gdbserver can be used in combination to provide debugging capabilities over the network.   gdbserver  is run on the machine you want to debug.   gdb  is run on the machine you want to debug from, usually your local machine. More  here . Before we get started, we need some software.  Alpine 3.8 will be the gdbserver. NFS We will be using nfs (Network File System) to mount a remote directory and have it look like a local directory.  We will cd to the nfs mounted directory which contains the program we want to debug before we launch gdb.  This way the program and symbols will match.  gdb will be running on your local client, but it will be launched when in a directory on the gdbserver's system. More than you wanted to know about  nfs . To set up nfs, you will need nfs software on your server and your client. SERVER  (Your Alpine machine) - Add nfs support: % apk add nfs-utils - Edit /etc/exports,
Read more

Build FFMPEG for Windows Using Visual Studio Toolchain

FFMPEG for Windows is built under MinGW or Cygwin.  We will be using MinGW. You may need ZLib, the ZLib provided with MinGW does not come with a .a file for some reason.  You can find ZLib at  https://zlib.net/ Build Zlib so that you get zlib.lib. Follow this page:  https://trac.ffmpeg.org/wiki/CompilationGuide/MSVC NOTE: When following the instructions on the above page, they only give a configure command for a release version, which is: ./configure --target-os=win64 --arch=x86_64 --toolchain=msvc If you want to do a full debug build, try this: ./configure --target-os=win64 --arch=x86_64 --toolchain=msvc --extra-cflags=" -EHa -nologo -D 'DEBUG' -D 'WINDOWS' -D 'HAVE_STRUCT_TIMESPEC' -D 'API_EXT_PARAM_LIST'" --enable-debug --disable-stripping --disable-optimizations --disable-cuda --disable-cuvid --disable-d3d11va --disable-dxva2 --disable-nvenc --disable-vaapi --disable-vdpau You should now be ready to use ffmpeg in a
Read more