sockets-for-pcl icon indicating copy to clipboard operation
sockets-for-pcl copied to clipboard

Published 20 hours ago • verified publisher icon rdavisau

How to install from source instead of NuGet

Open doubledunk opened this issue 9 years ago • 1 comments

Hello community, I hope your week is going well. I have an inquiry and I was hoping to pick someone's brain.

  1. If I was to add functionality to UdpSocketClient abstraction portable interface and class and to the platform specific implementations would I need to repackage it in NuGet format?

Thank you kindly,

doubledunk avatar Feb 01 '16 23:02 doubledunk

Hi @doubledunk

For testing/development purposes, it's easiest to reference the appropriate .dlls directly. For example -

  • you clone sockets-for-pcl
  • you make some changes to IUdpSocketClient then implement the changes in Sockets.Implementation.Net and Sockets.Implementation.WinRT, you compile and everything is :ok:
  • you want to play with these changes so you create new project of Windows Desktop and iOS and UWP (or whatever), and a PCL that they all reference
  • In each project you reference Sockets.Plugin.Abstractions plus the correct dll for that platform:
    • for the PCL -> Sockets.Plugin\bin\Debug\..
    • for Windows -> Sockets.Plugin.WindowsDesktop\bin\Debug\..
    • for iOS -> Sockets.Plugin.iOSUnified\bin\Debug\..
    • for UWP -> Sockets.Plugin.WindowsStore\bin\Debug\..

Then you can write the code in your PCL and the platform projects will use their correct .dll. This is effectively what happens automatically for you when you install the nuget package. Hope that helps! :star2:

rdavisau avatar Feb 02 '16 00:02 rdavisau