I have an application that consumes some libraries, developed by me, via NuGet packages. Before migrating to Net6 from .Net framework, I used to test the code changes of my libraries by simply replacing the dlls in the NuGet folder contained in the "packages" folder of the application. The dll are actually 2: one native c++ code dll and a C++/CLI managed dll that wraps it. After compiling, the modified dlls were copied to the bin folder and could be run. I liked this workflow as I could test the changes in my library code without creating a new NuGet package with a new version number each time (and without updating the application to a new package). After migrating to Net6 this has become impossible as there is no more a "packages" folder.Thank you very much,CR
I tried to replace the dlls in the .npkg file (editing it as a .zip) but the new code doesn't run. I think that the NuGet package is cached somewhere on my machine and a new package with a new version needs to be created in order to get the new code executed. Is there a way to avoid it?