Last post Mar 13, 2019 02:02 PM by ygoe
Mar 13, 2019 07:26 AM|ygoe|LINK
and providing the relative path to the library project directory.
Now Visual Studio has copied over the selected files. But I need to develop it further and make changes to the library source files.
How can I update them in my ASP.NET project? Adding them was easy with LibMan but now it left me alone. Restoring the libraries does nothing. Probably because they're already there, but outdated.
Do I need to copy the files myself again, from the library directory to the ASP.NET app directory? Then I don't need LibMan at all because if I have to copy the files manually every time from the second time on, I can just as well copy them manually the
first time, too.
Looks like the "filesystem" source in LibMan is completely useless and should have never been added.
(This was originally asked in the
Mar 13, 2019 12:20 PM|mgebhard|LINK
Can you explain the problem you are trying to solve?
Mar 13, 2019 02:02 PM|ygoe|LINK
LibMan can be used through the Visual Studio UI to install and restore client-side packages from different sources.
I am using it to install a client-side library I create myself, stored in the same solution directory (and Git repository), from that local filesystem location into a separate demo project.
The demo project is an ASP.NET Core project that uses the library to demonstrate it in a web GUI.
So I could use LibMan to successfully install the package into the demo app from the other project directory. But then it becomes useless. There's no update function that could re-install the once installed files with the changes I made. If LibMan can only
copy such files from a filesystem source once, and then never again, it would be easier to copy the files manually and not bother with LibMan.