You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on a user's experience in #smuxi-devel and my own experience when first using SmartIrc4net.
I propose removing StarkSoft proxy's source code from the tree, and adding NuGet package config references for log4net and StarkSoft's updated proxy code StarkSoft.Aspen.Proxy, then changing the namespaces in our code from StarkSoft.Net.Proxy.
This will allow users to just clone the repo, double-click the .sln and compile without any reference or assembly errors as NuGet will restore the missing dependencies automatically.
The text was updated successfully, but these errors were encountered:
log4net and nunit are nuget candidates yes, but StarkSoftProxy is a git submodule that gets automatically fetched if cloned the right way via git clone --recursive
Based on a user's experience in #smuxi-devel and my own experience when first using SmartIrc4net.
I propose removing StarkSoft proxy's source code from the tree, and adding NuGet package config references for log4net and StarkSoft's updated proxy code StarkSoft.Aspen.Proxy, then changing the namespaces in our code from StarkSoft.Net.Proxy.
This will allow users to just clone the repo, double-click the .sln and compile without any reference or assembly errors as NuGet will restore the missing dependencies automatically.
The text was updated successfully, but these errors were encountered: