Hi all-

Trying to build DNN from source so I can work on a module which for some reason requires dnn source in order to build itself.

I (think) I have everything set up, but I am getting massive numbers of build errors from dnn source when I try to simply build it with no changes.  I have to conclude my environment is still wrong -- the errors must be due to a setup mistake.

Here's what I have:  win7+sqlserver express 2008r2+vs2008sp1.  When I load the vs2008 version of the dnn sln, I get warnings that the dnn source files are not "trusted".  I have spend hours trying to find instructions on the net to mark the folders as trusted -- none of the instructions I've found seem applicable to my versions.  When I build anyway, I end up with 200+ errors -- mostly inability to access various labels.  Which makes me think it cant see untrusted files.

In any case, I am lost at this point - I have no idea how to proceed.  If anyone can point me to a good tutorial (one that is for DNN source please -- there are endless tutorials for setting up non-source versions, but they don't get me where I need to be).

Thanks,

Mark

As Wes already indicated, I cannot think of any module project which would require the DotNetNuke framework source to be installed for it be built. Instead you would add to the project a reference to the DotNetNuke.dll assembly (and possibly to other DotNetNuke related assemblies depending on the requirements of the module) located in the \bin folder of the website in which the module development is being done.

Regarding your specific issue with not being able to build the DotNetNuke_Community_VS2008.sln solution file without errors, there are several common causes for this problem:

1. There is no web.config file located in the website root folder. The source package includes a release.config and a development.config file. One of those (usually development.config) must be renamed or copied to web.config. Without the web.config file, many errors will be displayed as the various class imports statements contained in web.config will not be available to the compiler.

2. The solution file assumes a default website reference located at http://localhost/DotNetNuke_Community. Most likely that is not the site alias that you have used when setting up the website application in IIS. Before opening the solution file in VS, you must open it in a text editor (Notepad works well) and replace the reference to http://localhost/DotNetNuke_Community with that used for your the website alias you have setup in IIS. For example, to http://localhost/DNN5Source. While editing the solution file in Notepad you can replace other references to "DotNetNuke_Community" with that of your site alias. This is optional, however.

3. Make sure that the website application that you have created in IIS is pointing to the Website child folder of the folder containing the extracted source package.

4. If you look at the VS Configuration Manager for the solution you will see that the website itself is not checked to be built. That is correct as it is not currently possible to pre-compile the website. If you do try to build the website, a number of errors will be displayed.

5. Upon building the DotNetNuke solution, you may see a number of warnings, often due to references to deprecated (obsolete) methods. Those are OK and will not prevent you from building the solution. With each version, the number of warnings become fewer. As I recall when building the DotNetNuke v 5.06.01 solution file in VS2010, I did not see any warnings displayed.

After reading your initial post I was about to direct you to the DotNetNuke Wiki for more information on doing a source package install but realized that the Wiki does not contain such information. I wrote a detailed set of instructions for a source installation last night off-line and expect to get these uploaded to the Wiki later today.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

Hey Bill,

Nice add - one comment - as its been a while since i stuffed round with rebuilding the source - are there still potential version issues from libraries that update their version numbers automatically - I seem to recall way back in the dark ages that this used to cause some wierd issues with dlls getting out of sync with version numbers - specially between development and production servers.

Westa