Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...DNN 7 Install ErrorsDNN 7 Install Errors
Previous
 
Next
New Post
11/30/2012 9:23 PM
 
Richard White

Joined: 12/20/2007
Posts: 19
I am running my development system on Windows 8 pro with Visual Studio 2012 Pro. First ... build errors ------ Build started: Project: f:\...\rickwhite_700\, Configuration: Debug Any CPU ------ Validating Web Site Building directory '/rickwhite_700/App_GlobalResources/'. Building directory '/rickwhite_700/admin/Containers/'. f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\Toggle.ascx.cs(54,25): error CS0501: 'DotNetNuke.UI.Containers.Controls.Toggle.Class.get' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\Toggle.ascx.cs(54,30): error CS0501: 'DotNetNuke.UI.Containers.Controls.Toggle.Class.set' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\PrintModule.ascx.cs(57,35): error CS0501: 'DotNetNuke.UI.Containers.PrintModule.PrintIcon.get' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\PrintModule.ascx.cs(57,40): error CS0501: 'DotNetNuke.UI.Containers.PrintModule.PrintIcon.set' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\Title.ascx.cs(52,34): error CS0501: 'DotNetNuke.UI.Containers.Title.CssClass.get' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\Title.ascx.cs(52,39): error CS0501: 'DotNetNuke.UI.Containers.Title.CssClass.set' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\Visibility.ascx.cs(131,37): error CS0501: 'DotNetNuke.UI.Containers.Visibility.BorderWidth.get' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\Visibility.ascx.cs(131,42): error CS0501: 'DotNetNuke.UI.Containers.Visibility.BorderWidth.set' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\Visibility.ascx.cs(161,33): error CS0501: 'DotNetNuke.UI.Containers.Visibility.minIcon.get' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\Visibility.ascx.cs(161,38): error CS0501: 'DotNetNuke.UI.Containers.Visibility.minIcon.set' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\Visibility.ascx.cs(164,33): error CS0501: 'DotNetNuke.UI.Containers.Visibility.MaxIcon.get' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\Visibility.ascx.cs(164,38): error CS0501: 'DotNetNuke.UI.Containers.Visibility.MaxIcon.set' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\Icon.ascx.cs(55,37): error CS0501: 'DotNetNuke.UI.Containers.Icon.BorderWidth.get' must declare a body because it is not marked abstract or extern f:\Visual Studio 2012\WebSites\rickwhite_700\admin\Containers\Icon.ascx.cs(55,42): error CS0501: 'DotNetNuke.UI.Containers.Icon.BorderWidth.set' must declare a body because it is not marked abstract or extern Validation Complete ========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ========== Then ... during the actual install process constant errors when the install is attempting to update the progress bar. InstallWizard.aspx line 1060 installWizard.progressBarIntervalId = setInterval(function () { $.getInstallProgress(); }, 100); SCRIPT1014: Invalid character jquery.min.js, line 2 character 10807
 
New Post
11/30/2012 10:01 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253

You do not need to build and install the DotNetNuke source package for module and other extensions development as it is not recommended that you alter e code primarily because later upgrades of the framework will prove to be very difficult if not impossible. Use the install package, Starter Kit, etc. instead.

If you should decide to build and install the source package to better understand the various API's or for stepping into the source code when debugging one of your module development projects, the following Wiki entry that I wrote a couple of years ago should help:

http://www.dotnetnuke.com/Resources/W....

Note in particular that you must rename development.config or release.config to web.config prior to building the solution. Do not include the website project (localhost/ . . .) in the projects to be built. It will be compiled automatically (just-in-time compile). All of the other projects must be built before following the usual DNN install procedures.

Also note that DNN 7 requires running in a ASP.Net 4.0 or 4.5 application pool (integrated pipeline not classic) and SQL Server 2008 or 2012.

I have built and installed the various DNN 7 CTP, Beta, RC and Release source versions several times without any of the errors you noted so know that the steps outlined in the Wiki work when followed carefully.

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
 
New Post
12/1/2012 12:09 PM
 
Richard White

Joined: 12/20/2007
Posts: 19
Thanks for the info William. I'm wondering if I've been doing things incorrectly all along. Ever since DNN 4 my process has been to use the Visual Studio Starter Kit to create a project in Visual Studio and run all my development work using the Cassini web server. That's what I did here too. Is that wrong?
 
New Post
12/1/2012 3:05 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253

Richard,

I'm not too familiar with the DNN starter kit as I use my own templates for module development. As for the built-in web server (Cassini) for VS, I have always preferred to use IIS (v7.5 currently in Windows 7) in part because I like to be able to run the development site outside of VS and found Cassini to be very slow. DNN 7 now requires the intallation's application pool to be running ASP.Net 4.0 or 4.5 in integrated pipeline mode. I'm not sure that VS 2012's Cassini web server can handle integrated pipeline mode. I did some Google searching just now but did not fine a definitive answer. It was quite clear that VS 2010 Cassini could not.

Other than IIS, you might also consider IIS Express 7.5 (or later in Windows 8) which I understand can handle integrated pipeline mode.

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
 
New Post
12/12/2012 7:49 PM
 
Mike Fulton


Joined: 11/30/2012
Posts: 4
I was having the same problem as the OP and after reading the responses I am massively confused about how this is supposed to work.

The first questions that come to mind are why create and distribute a Visual Studio project template and then tell us we're not supposed to build the project created from it? And why distribute something that throws errors when you try to build it?

In Visual Studio, is there any point to selecting:

"New Web Site" -> "Dot Net Nuke Application Framework"

'cos at this point it doesn't seem like there is.
 
 Page 1 of 3
123Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN 7 Install ErrorsDNN 7 Install Errors


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