This should be added automatically if you're using Nuget. You don't need to directly target that. In fact, I don't think you can.

I'd recommend updating your Nuget references to being the most current they can be for your development environment, and then checking that all of the Nuget references are targeting the same version of DNN Platform. :)

Will,
I am using a clone of the nuget directory for release 9.6.2 or 9.7.2. The error comes for initializing MS Visual Studio. If I look into the nuget.config file, and follow the links there is no mention of the ClientDependency code.

I am trying to compile the base DNN version, so that I can implement the new Azure email service.

I think that I can update the references in the code to the correct version of the ClientDependency.Core.dll file; but I don't think that I would be able to compile the code.

Any idea on how to work around this?

Thanks for your responses ....
Hans

Oh, you're trying to compile DNN itself?  You'll want to follow the steps described in the video series linked below.  

https://www.youtube.com/w...jVAt50ORp1TIIiaeLtq2

DNN is not a hobbyist platform and instead is better suited to larger companies and enterprises.  For those reasons, the build process is not as simple as open and build.  You'll have a tiny bit of setup, but once you go through the videos, you'll be good.  

Now, I do want to put out a disclaimer...  

It's not a good idea to download and/or build the DNN source code unless you're intending to build in new features and/or fix bugs to submit as a Pull Request (PR).  The primary reasons include: 

• The source code is not necessary to build or debug anything (unless it's a deeply rooted bug in DNN); 
• Any extension can be built and debugged without DNN's source code; 
• If you need to look at the source code at any point in time for any reason, it's always available on GitHub; 
• Having the source code ready to build encourages people to make core code changes (this is not a best practice).  

Making core code changes can be okay if you're never ever ever ever going to upgrade in the future.  In this scenario, you'd be forking DNN and would be responsible for making any and all updates moving forward.  This is because any upgrade from that point will either be overwritten - or fail and crash the website immediately.  

With that being said, please feel free to work with DNN in any way that meets your needs.  :)  

Will,

Thank you for the response. Just a short note regarding your note of caution. I am fully aware of the dangers of working with the DNN source code. I have and will continue to with and learn from Peter Donker's excellent video series.

Awesome! 

FYI - It wasn't necessarily just for you.  ;)  My responses are also written in a way that knows anyone can potentially see it in the future, so it's just a normal message to be sure to educate those who aren't aware of the dangers.  A lot of people just decide to open the source code and get to work. 

For example, we're literally just wrapping up a 3-year consulting engagement with a client where the core code changes were so significant over the years, we've had to slowly remove them over the course of a handful of (modified) upgrades.  About half the updates were things that would've been gained from upgrading too.  [facepalm]  It was a nightmare, but it's finally (almost) over.  :)  

I'm happy to help and happy coding!