I am finding it impossible to compile the sources project(s) for versions 3.05.01, 3.05.00 and 3.04.00.

I am using DNN v4.9.1, Visual Studio 2008, SQL Server 2005, IIS 7 running on Windows Vista Business.

The problems range from the solution/project files having outdated references (using project-to-project web references) in 3.04.00, to 3.05.00 and 3.05.01 having project references that are just plain missing.

We are attempting to deply the DNN blog to a client web site, and we need to make some minor changes that require us to make changes to the codebehinds. We cannot move forward with these broken projects. Assistance is urgently needed.

Please note the blog module functions correctly as installed. It is our attempts to rebuild the module (even without modifications) from the source.

Assistance in the form of clear setup instructions is urgently needed.

Mike Ryan

Thanks, but the problems are a bit deeper than that. Problems that I've found with the 03.05.01 source:

1. The resource (.resx) files are located in the App_LocalResources folder, but the project/solution is expecting them to be in the same folder as the source files they're supporting.
2. Several reference files are just plain missing from the 03.05.01 source, and I had to go into older versions of the source to find them. The blopostredirect.aspx.resx was nowhere to be found as far back as the 03.03.00 source. In the end I just created a file for it, since there didn't seem to be any actual resources referenced in it.
3. There are two different solutions in the source: DotNetNuke.Blog.sln and DotNetNuke.Blog.Build.sln, with no indication of which is supposed to be used for what. The .Build solution is rather broken, depending on a none existent DotNetNuke.Blog.BuildSupport project. My solution, ultimately, was to ditch the solution files and work with the projects directly.
4. Without the solution files, I was forced to install the blog source in a development installation of DNN, and use one instance of VS (opening DNN as a web site) if I wished to edit .ascx files in the designer view, and another VS instance (opening the DotNetNuke.Blog project) to edit and compile the code.
5. I don't know if it's an odd configuration of the project, or due to missing information from the solution files, but I'm unable to do a release compile of the DotNetNuke.Blog project, only of a debug compile.

I've been able to make the changes we needed to make to the source and get it to compile and work in our production environment, but I have to say, I find that the source installation of the recent versions of the DotNetNuke.Blog module to be unusable "as is". I hope my issues presented above help improve these issues.

Hi all,

while I write this, the entire project structure and project files/solution files are being completely rewritten. We are confident that the new setup will make compiling much easier and straightforward.

Best regards,
Dario Rossa