When we develop things locally and want to test and maybe even debug through code we deploy packages locally. The reason for this is that our code is spread across multiple repositories and we leverage lower order components in layers above.
This experience is not consistent and is error prone. We need to improve on this, make it simpler - consistent and well documented on how to do this.
For instance for .net - an idea could be to create a simple NuGet server that is a bit clever. Instead of having to deploy packages locally to the %HOME%/.nuget/packages as we do today, we might be able to crate a simple NuGet server that could serve packages on the fly from where the assemblies are being built.
When we develop things locally and want to test and maybe even debug through code we deploy packages locally. The reason for this is that our code is spread across multiple repositories and we leverage lower order components in layers above.
This experience is not consistent and is error prone. We need to improve on this, make it simpler - consistent and well documented on how to do this.
For instance for .net - an idea could be to create a simple NuGet server that is a bit clever. Instead of having to deploy packages locally to the
%HOME%/.nuget/packagesas we do today, we might be able to crate a simple NuGet server that could serve packages on the fly from where the assemblies are being built.┆Issue is synchronized with this Asana task