Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing source packageInstalling source package
Previous
 
Next
New Post
6/18/2014 11:14 AM
 

I just finished working through problems installing the 7.2.1 source package on Windows 7, SQL 2008 and VS 2010. I was following the instructions found at http://www.dnnsoftware.com/wiki/page/.... I thought I would share my experience.

  1. You may find that the assembly references to the Microsoft WebAPI (System.Web.Http, System.Web.Http.Formatting, System.Web.Http.WebHost) and also System.Net.Http in most, if not all, projects aren't found. I assume that this works for some people because they have the WebAPI installed in the GAC (or there is another way for VS to resolve those references that I'm not aware of.) In some project files (.csproj) there is no hintpath given for the reference. In others, the hintpath is to a non-existant "Components\WebAPI\" folder. I modified the .csproj files to provide a hintpath to the dlls in the Packages folder to fix this. The Wiki mentioned above has you edit some things in the solution file before opening it in VS. You may as well just edit the .csproj files to fix the reference too. This seems to have been reported here but nothing has changed in the source package for 7.3.0. I had some problems with other assembly references but I may have created those as I tried to resolve this issue. I didn't start over from scratch to try to reproduce them.
  2. You are supposed to compile the solution in Release mode before launching the DNN install. Even if you want to debug it, compile in Release, then compile in Debug, then do the DNN Install. This is discussed at http://www.dnnsoftware.com/forums/for....
 
New Post
6/19/2014 2:14 PM
 
thanks -I'm not sure about the first as I don't have a machine with only vs.net 2010 to test on, but suspect you're right and few people have noticed i.e. everyone is either using vs.net 2012 or 2013 both of which install WebAPI/MVC, or had installed WebAPI/MVC separately. As to the 2nd, I hope to update the wiki soon to make this more obvious - compiling in release first has been what we've done for more than 5 years but people still seem to miss it

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing source packageInstalling source package


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out