You probably need to add a reference to the DotNetNuke.dll found in your installation's bin folder.

My instructions are pretty specific about the paths to use. If you diverge from those paths, then references start to get funky

I tried to move it to "C:\Websites\dnndev.me" and update Visual Studio, but it didn't help.

Posted By Joe Craig on 13 Nov 2019 12:50 PM
You probably need to add a reference to the DotNetNuke.dll found in your installation's bin folder.

Didn't help.

 

 

Posted By Chris Hammond on 13 Nov 2019 02:22 PM
My instructions are pretty specific about the paths to use. If you diverge from those paths, then references start to get funky

I followed your instructions precisely, but I still stumbled upon same complile error. What did work for me is I scrolled down and after multiple errors about DotNetNuke namespace there was warning (WARNING, CARL! NOT EVEN ERROR!) about that DotNetNuke.dll was compiled using .Net Framework 4.7.2 (DNN version was 9.4.x) and project's target .Net Framework version is 4.5.x. So I needed to change that in project settings. Also I finally stumbled upon your instruction about fixing DNN theme creation errors. Since it happens all the time, you should really include that fix into installation instruction. Before I stumbled upon that video I wasted many hours on research.

Just in case someone needs that fix: https://www.youtube.com/w...0spov4It4Z8fswIbNZFd

First 5 minutes are about wrong path "C:\website\..." instead of "C:\websites\..." and how to cut/paste folder in Windows, second half of the video is actual fix.

 

Hi Constantine,

First of all: welcome to DNN :-)
Second: as I understand you want to create a new theme. My first recommendation would be to play around with the default theme that is shipped. Just to get to know DNN, the skin controls, containers etc.
If you want to step up your game, you might want to take a look at https://github.com/nvisionative/nvQuickTheme.
The documentation is on https://nvisionative.github.io/nvQuickTheme/ and there is also a recording of a session on DNN-Connect that you can find on https://www.youtube.com/watch?v=gFLjScoomQw

When you get the hang of it, you'll find typical issues in/on other themes more easily as most developers have their own take on their work.

Hope this helps with future activities.

Cheers
Tycho

This worked for me. I needed to add references for DotNetNuke.dll and Microsoft.ApplicationBlocks.Data.dll.

And nowadays most people refer to the nuget packages instead of local library references. But if you do, you need to also make sure the build process does not publish those files to mess up your development environment.
Themes that don't really use C# don't really need to have any references (which is very often the case for a theme).