Referencing Net Core Libraries and getting dependencies

  • Thread starter Thread starter reeset
  • Start date Start date
R

reeset

Guest
With Windows.Forms and WPF moving into Core 3, I've been looking at a couple projects and testing the process of shifting from targeting the 4.7.2 framework to the Net Core 3. In using the Analysis tool, the core executable and all reference libraries appear to be good candidates for this work and indeed, all were easily converted and compile fine. My question...

The project in question has an executable and 4 libraries. They reference in the following manner:

* Executable

** Lib 1 (dependency of Exe)

** Lib 2 (dependency of Exe)

*** Lib 3 (dependency of Lib 2)

In Lib 3 -- I have to make use of a handful of Encodings -- so I add the assembly that provides extended codepage support to Net Core. My problem, when I compile the Exe, and try to run it, it when a function from Lib 2 calls Lib 3 and makes a call to the codepage dependency, it fails. I was assuming that when I referenced the assembly, the dependencies for these assemblies would be pulled as well.

It looks like just referencing the Release build isn't the proper way to make sure all the necessary dependencies get pulled. Is there a set of documentation that would walk me through this scenario and the expected approach. Long-term, this project has close to 20 libraries that will be referenced, and many of these references have dependencies -- so I need to figure out how to solve this simple example so I can move forward in my testing.

Thanks

--tr

Continue reading...
 
Back
Top