Can I change something in an existing package without copying anything and be sure it will recompile?
Even though we don’t recommend it and strongly encourage you to work on the source package, you can edit a nuget package if need be:
- Mark that package as editable with
--editable-packages Foo.Bar - Make your changes
- Restart vvvv without the
--editable-packagescommand line argument but with the--nocacheflag to ensure all packages get re-compiled and the internal cache updated. - Restart vvvv once more without any flags
Or does this only work for packages where I don’t need to compile a C# solution?
A nuget package doesn’t come with a C# solution. Not sure this is related.
I was eventually able to fix the bug and run the library with the fix
You most probably missed step 3). Our system assumes that nuget packages don’t get modified by the user. It therefor does not compare checksums on startup which it would do if you’d follow the recommended source package workflow.
Maybe add more about No Cache to the article?
Not sure we should encourage this workflow any further in our main documentation. The probablitly to lose work / introduce nasty bugs is super high, especially if your changes happended a few weeks back.
I’d like to be able to continue using the package compiled after editing to speed things up
It should like outlined in step 1-4
where does “compile source packages” come from
This was an older concept and should be removed from the launcher. It was replaced with the editable packages concept.