Archive
Monthly
Go
|
|
DNN Blog
Jun
1
Posted by:
Chris Hammond
6/1/2010 6:38 PM
So this is the first in a series of promised blog posts that I am long overdue on! These posts are a follow up to a Beginning DotNetNuke Module Development webinar that we provided back on May 17th. If you didn’t attend the webinar you missed out, but you do get to benefit from these blog posts if you want to easily get setup and running with C# module development for DotNetNuke.
- This post
- Customizing and installing a C# module development template
- Configuring NAnt to package your DotNetNuke Modules (replaced with MSBuild, see next item)
- Using MSBuild instead of NANT
This first post will be discussing the development environment that I configure when I am doing DotNetNuke module development, in addition to this post I’ve got a post about a free Visual Studio template that I am releasing on Codeplex that makes setting up your first DNN module very easy. As well as another blog post about using NANT to automate the packaging of your DNN modules so that you can easily deploy them to other environments.
In this series we will configure an environment that works well for individual or team development, using the WAP (web application project) model for our projects in Visual Studio. Each developer will have their own local installation, their own instance of SQL server (at minimum their own database on a shared SQL instance). You can go through this process using Microsoft SQL Server Express, but I would suggest using a development or other licensed version of SQL Server as Express can be a real pain in the rear some times.
There are a few assumptions made in this configuration.
- You have Visual Studio 2008 SP1 installed (You are likely fine without SP1, but you might as well upgrade!)
- You have IIS installed on your Operating System and ASP.NET extensions are installed and enabled.
- You have .NET 3.5 SP1 installed (generally available via windows updates)
- You are using SQL 2005/2008 (not express)
So let’s get started:
Setting up your development environment.
Setting up your development environment can vary based on what your end goal is. If you are doing module development for your own use, and within your own DNN environments, you can ignore a few of the settings below. If you are doing module development with the idea that you might turn around and give the modules away, or sell them, then you will likely want to follow the guidelines set forth below to support the widest array of DNN installation environments.
Choosing a DotNetNuke Version
Choosing a version of DotNetNuke is important when you start your development for couple of reasons. For modules that you are developing for yourself, you need to ask, what is the minimum version of DotNetNuke that you have in production. Are you running DNN 4.5.5? Are you running 4.9.5, 5.2.2 or 5.4.2? Based on the answer you can determine what version of DNN you should setup as your development environment. You shouldn’t be developing on a newer version of DNN than what you have running in production. As with everything there are ways around this, but I am not going to go into the details on that in this blog post.
As a developer working to create modules and release those, you might have production sites that are running on the latest and greatest version of DNN, but what about your customers? Or your potential customers? You have to ask yourself, do you want to provide support for really old versions of DotNetNuke? From a development perspective you will probably say no, but from a business perspective, you might say yes, and here’s why. Not everyone upgrades DotNetNuke websites as they should, and often times you will find that some people never upgrade. While I don’t advise taking that approach to managing a DotNetNuke website, it is a fact of life that people don’t always upgrade and there are thousands of people, if not tens of thousands, that have sites that aren’t running on the latest version of DNN. You should take that into account when you are doing your module development, if you compile your module against an older version of DNN then your module should run on newer versions of as well, for example. If you compile your module against DotNetNuke 4.5.1 it will likely run on every version of DNN released since then. Though there are extended cases where this won’t always work, DNN strives to maintain backwards compatibility, this isn’t always possible.
You might also want to use features that are only available starting with a specific version of DotNetNuke, such as the workflow functionality found starting in DNN 5.1, in that case you may choose not to support older versions of the platform out of necessity. This will minimize the market in which you can sell your modules, but also can make for less support and an easier development cycle due to the features that DNN provides.
Choosing a Package
Now here’s one that may baffle you a bit. I’m going to recommend that you use the INSTALL package for whatever version of DotNetNuke that you download. What? The INSTALL package? What about the SOURCE package? Well you can use the source, but you don’t need it. The module development that I’m setting you up for doesn’t require source, and overall makes things cleaner. We aren’t going to be opening the DotNetNuke project when we do our module development, so why have the files sitting around for nothing?
The steps for setting up your development environment will apply to both the Community and Professional editions of DotNetNuke.
Installation Configuration
Once you have the version selection out of the way you can go through the installation process. While I’m not going to walk you through the minutest of details of each step of installing DotNetNuke in this post, I will at least try to point you in the right direction for each step. In future writings I will be doing a series of posts about installing DotNetNuke in various environments that will go into further details. This post half assumes that you have configured DotNetNuke before.
- Download - Download the INSTALL package of the version of DotNetNuke you want to use in your development environment.
- Extract - Extract the files in the INSTALL package to a location of your choosing, this location is where you will point IIS (the web server) when we can configure the website. In my example I extracted to c:\websites\dnndev\ (One item of note: you may need to right click on the ZIP file and choose Properties before extracting, on the properties window if you have an UNBLOCK option click that. Some versions of Windows have started blocking files within the DotNetNuke ZIP files, which will cause you problems later during the actual install.)
- Setup IIS – IIS is the web server that comes with Windows computers. In our example we’re going to create a new Website in IIS 7.5 on Windows 7, this isn’t possible in Windows XP because of limitations with IIS v5.1, but is possible in other versions of IIS. You should create a new website, and point to the folder where you extracted the INSTALL package. If you are using IIS 5 or IIS 6 you will need to verify that ASP.NET 2.0 is selected on the ASP.NET tab. I am setting up a website so that I can access http://dnndev/ for my development environment, to do this you must configure the HOSTS file in step #4. You may notice in my screen shot that my Application Pool is setup to Classic .NET AppPool, by default your application pool will have a custom name (in IIS7.5), you can change this if you wish. I do this because of a problem my laptop has with the dynamic accounts that IIS tries to run under. See step #5 for more info about configuring the permissions.
- Modify the HOSTS File – In order to be able to access http://dnndev/ in our web browser we need to change the HOSTS file located in the c:\windows\system32\drivers\etc\ folder. You can open this HOSTS file with NOTEPAD or any other text editor. By modifying this file we essentially tell the computer that when we make a request to http://dnndev/ we should use the local IP address. See the screenshot for what this file looks like. Once you save this file you should restart your web browser to ensure that it has the latest settings.
- Set File Permissions – Setting up the file permissions for your DNN install is often the step that causes the most trouble. You should right click on the FOLDER in which you extracted DNN (c:\websites\dnndev\) and choose properties. Choose the Security tab (if you don’t have a security tab you are likely using Windows XP and need to uncheck the Use Simple File Sharing option in the Tools/Options screen). You need to add permissions for the account in which your website is running under. You will want to setup the permissions to give the account Full or Modify permissions for the DNNDEV folder. Which account you will use will vary based on your version of IIS, here’s a simple grid to see what the default account is for your version of IIS
| IIS Version |
Operating Systems |
Account |
| IIS 5, IIS 5.1 |
Windows 2000, Windows XP |
localmachine\ASPNET |
| IIS 6, IIS 7 |
Windows 2003, Windows Vista, Windows Server 2008 |
localmachine\Network Service |
| IIS 7.5 |
Windows 2008 R2, Windows 7 |
IIS AppPool\ |
If you are using IIS7.5 you’ll notice in the above table , this is because when you setup a new website in IIS a new application pool is created. In place of you should type in the name of the application pool that was created (automatically during step 3). You can also bypass this and configure your application pool to use the Network Service account instead of a dynamic account, that is generally how I configure my environment.
- Create Database – In SQL Server you should go through and create a new database. I always create a database with the same name as the website, so in this case DNNDEV. Once you have created the database, create a user that can access that database. I always use SQL authentication, turn off the enforce password requirements, and give the user DB Owner and Public access to the DNNDEV database. Remember the username and password you create here as you will need them when you walk through the installation process.
- Access the Installation Wizard – Now you get to walk through the easy portion of the installation. You should load up your website in a browser, http://dnndev/ this may take a few moments, but when it does you’ll come to an installation wizard screen. Choose the Typical option and step through the process of installing DNN. When you come to the database configuration screen you should choose the SQL 2005/2008 option, uncheck integrated authentication and populate the name of your SQL Server (likely (local), ., or IPADDRESS), Database Name (DNNDEV), Username and Password. Now there are two additional options you can configure, normally I would tell you not to modify these, but from a development environment perspective I do recommend that you change the objectQualifier setting. It should be blank by default, you should type in “dnn” (without quotes), this will prepend “dnn_” to all of the objects that get created by DNN such as Tables and Stored Procedures. This is not something I recommend from a production stand point, but if you are developing modules for sale, then supporting objectQualifier in your development is recommended. It will save you time down the road if you have a customer who has an objectQualifier defined on their production databases. Step through the rest of the installation screens, you should remember your HOST and ADMIN passwords that you define as you get to those screens, you will need these when you login to your site later.
- Modify the Web.config File – One last thing we need to change in our development environment is to configure a setting in the web.config file. There’s a setting called ShowMissingKeys which is by default set to False, from a development perspective I recommend setting this to be True. This will make it so that any text in DotNetNuke that is localized will be displayed with an [L] in front of it, to show you what is localized and what is not. This is important if you are trying to create modules that can easily be customized for other languages, the ShowMissingKeys flag will also cause DNN to throw a message in place when a string that should be localized is missing from the Resource Files (resource files are XML files that contain the language definitions for localization).
You now have your DotNetNuke Development Website configured. In the next blog (coming soon) I will cover the configuration of the C# Module Development Template for Visual Studio and initial project creation using this template.
When released the template will be located at http://christoctemplate.codeplex.com/
To learn more about DotNetNuke in our instructor led classes check out the DotNetNuke Training page.
43 comment(s) so far...
Re: My DotNetNuke Module Development Environment
Great post ... I would also suggest setting up a test SMTP server as per Joe Brinkmans post. See blog.theaccidentalgeek.com/post/2009/09/22/DotNetNuke-Tips-and-Tricks-14-Testing-Emails-in-a-Dev-Environment.aspx
Paul.
By Paul Scarlett on
6/1/2010 7:02 PM
|
Re: My DotNetNuke Module Development Environment
Chris, I hope you can provide an example of a development environment where the web server and the Visual Studio installation are on 2 separate machines. Is this even possible?
By simonduz on
6/1/2010 8:01 PM
|
Re: My DotNetNuke Module Development Environment
Simon, I am sure it is possible, but I have no intention of ever trying it :)
Using the template I am releasing later this week you can build as much as you want without having DNN installed, but connecting to the server and doing debugging I hear is always a pain in the rear, so I always preach the method of developing in your own sandbox.
By Chris Hammond on
6/1/2010 8:02 PM
|
Re: My DotNetNuke Module Development Environment
An alternative to setting up an test SMTP server, is to just specify a drop location in your file system.
By Jay Mathis on
6/2/2010 4:31 AM
|
Re: My DotNetNuke Module Development Environment
is this possible? nice
By LeoTechnoSoft on
6/3/2010 8:30 AM
|
Re: My DotNetNuke Module Development Environment
I am not sure what I am doing wrong, but Visual Studio 2008 gives me first a warning:
The local IIS URL dnndev/DesktopModules?JuniorPlayers specified for Web Project JuniorPlayers has not been configured. In order to open this project the virtual directory needs to be configured. Would you like to create the virtual directory now?
When "Yes" is selected I get: Creation of the virtual directory dnndev/DesktopModules/JuniorPlayers failed with the errer: Could not find the server 'http://dnndev/ on the local machine.
I am running vista ultimate sp2 and IIS 6.
Any suggestions?
By Darnell Greer on
9/18/2010 11:32 PM
|
Re: My DotNetNuke Module Development Environment
Darnell, do you have IIS setup with a website running on DNNDev? Also, I think Vista comes with IIS7?
By Chris Hammond on
9/18/2010 11:33 PM
|
Re: My DotNetNuke Module Development Environment
No, I don't have a website up and running on dnndev. I think I may have missed something if it is a server. I am currently downloading iis7 to see if that will fix things. I am a low level intermediate at this and a little behind in my readings, so forgive me for not being up to date.
By Darnell Greer on
9/19/2010 6:25 PM
|
Re: My DotNetNuke Module Development Environment
Darnell, the instructions I posted above use DNNDev and talk about how to set that up. If you've setup DNN in another way you will need to use a different path for the project information
By Chris Hammond on
9/19/2010 6:25 PM
|
Re: My DotNetNuke Module Development Environment
Great! I can create the project in VS2008 now. I was trying to set up dnndev under the default site. Now it is its own. I still need to figure out how to get it to open under dnndev. Right now the iis 7 page comes up instead when I type in the browser. But getting closer.
By Darnell Greer on
9/20/2010 9:22 PM
|
Re: My DotNetNuke Module Development Environment
Chris, step 3 is a bit confusing, I guess because I just migrated from xp to window 7. I understand that I need to create a new site and if I get this right, in IIS Manager I right click on Sites and select Add New Web Site. From the screen shot you included it seems that you use port 80 but for this to work do I have to remove or stop the Default Web Site that is also on port 80?
Also In your advanced settings I see that your field Bindings says: http:*80:dnndev while mine says: http:*80: Any reason why this is happening?
Last, if I developed other web applications using VS and Dreamweaver, does changing the default web site to dnndev will cause any problems?
By Eric Chabot on
9/27/2010 3:22 PM
|
Re: My DotNetNuke Module Development Environment
Eric, if you don't type in the name DNNDEV and just use the catch all, then yes, you will have to disable the default website. I created a new website, and put in DNNDEV for the URL.
By Chris Hammond on
9/27/2010 3:23 PM
|
Re: My DotNetNuke Module Development Environment
Thanks for the quick reply that got me setup properly. Last thing, I also listened to your video (Basic DotNetNuke Module Development Video) and for some reason when I try to create a new project (vs 2010) , I select your template but the available fields at the bottom are different. In my case I only get the name, no location or else (see www.clemex.com/bug/myNewProject.png) compare to yours (www.clemex.com/bug/chrisProject.png) .
By Eric Chabot on
9/28/2010 10:30 AM
|
Re: My DotNetNuke Module Development Environment
Eric, that is definitely weird, I just tested in VS2010 and I see the fields I would expect, not what you see. What version of VS2010 are you using? Express?
By Chris Hammond on
9/28/2010 10:31 AM
|
Re: My DotNetNuke Module Development Environment
I installed the Visual Studio 2010 Ultimate from the MSDN package.
By Eric Chabot on
9/28/2010 12:22 PM
|
Re: My DotNetNuke Module Development Environment
Eric, that is weird, something is definitely missing. Do any of the other project types show extra fields?
By Chris Hammond on
9/28/2010 12:22 PM
|
Re: My DotNetNuke Module Development Environment
hum I think the other templates are ok but see for yourself just in case by watching this quick screen recording: www.clemex.com/bug/DnnTemplate/DnnTemplate.html
Can I have the wrong template?
By Eric Chabot on
12/10/2010 2:10 PM
|
Windows Server 2008 R2: IIS 7.5 App Pool, DNN 5.6.0
I couldn't start the installaton, i had the following errors:
File \\farm1.adhost.lan\live_inetpub\wwwroot\host2008\xxxx.domainname.co\Portals\_default\\Logs\LogFailures.xml.resources
Error Access to the path '\\farm1.adhost.lan\live_inetpub\wwwroot\host2008\xxx.domainname.com\Portals\_default\Logs\LogFailures.xml.resources' is denied. The Windows User Account listed below must have Read/Write Privileges to this path.
and error
System.Security.SecurityException: Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed
I made the following configurations:
IIS
--> Application Pools --> DNNDEV (the app poll name, can can be different) --> Advanced Settings… --> Load User Profile: Set to True
Server Manager
--> Configuration --> Local Users and Groups --> IIS_IUSRS
--> Add… --> IIS APPPOOL\DNNDEV
File Explorer
--> Open " C:\inetpub\wwwroot\DNNDEV " (can be different) --> Rightclick on "DNNDEV" Folder --> Properties --> Security --> Edit… --> IIS_IUSRS --> Permissions "Full control"
After this configuration, I terminated the w3wp.exe processes. After that I could install DNN with no problems...
By Roli Kreis on
12/10/2010 2:10 PM
|
Re: My DotNetNuke Module Development Environment
Roli, you need to add the user IIS APPPOOL\DNNDEV to the permissions for the file system, did you miss that part initially?
By Chris Hammond on
11/18/2010 10:31 AM
|
Re: My DotNetNuke Module Development Environment
Eric there is a setting in VS Ultimate to turn on project properties when creating.
By Chris Hammond on
12/10/2010 2:11 PM
|
Re: My DotNetNuke Module Development Environment
I am having trouble with Step 3. I am running on Vista with IIS 7 and I can't figure out how to set up the bindings so that the entry in the hosts file goes to the proper web site.
Based on your screen shot of IIS 7.5 (advanced setting), IIS 7 settings for the bindings is quite different.
In my case I am set up under C:\inetpub\wwwroot\DotNetNuke
In IIS7 I created a DotNetNuke app under the default web site that points to this location. I can get to the web site using localhost/dotnetnuke/
but for the life of me I can't figure out how to get dotnetnuke to get there.
I have been trying to get this to work for weeks (I know I'm pathetic).
Any help would be really dearly appreciated.
Dave
By Dave Diguer on
12/12/2010 10:44 PM
|
Re: My DotNetNuke Module Development Environment
Dave, Windows Vista is almost exactly the same as Windows 7, you need to bind a new WEBSITE, not a virtual directory as you've done with localhost/dotnetnuke
By Chris Hammond on
12/12/2010 10:45 PM
|
Re: My DotNetNuke Module Development Environment
Re Jeff Sullivan's comment about " you must install IIS 6 Metabase and IIS 6 configuration compatibility."
This is something that you can configure by going to Programs and Features and the "Turn Windows Features on and off" link. Open up the section that refers to IIS and you'll find the features. While I was there, I turns lots of things on ...
By Joseph Craig on
12/21/2010 11:04 PM
|
Re: My DotNetNuke Module Development Environment
Now I am stuck. I'm using VS2010 and Win 7.
When I try to start VS in Debug mode, I get "Unable to start debuggin on the web server. The web server is not configured correctly. See help for common configuration errors."
Any ideas? I haven't made any sense from the Help that is delivered ...
By Joseph Craig on
12/22/2010 10:54 AM
|
Re: My DotNetNuke Module Development Environment
Joe, you likely need to make sure the IIS Metabase stuff discussed in the comments here is enabled
By Chris Hammond on
12/22/2010 10:55 AM
|
Re: My DotNetNuke Module Development Environment
Re the problem in my last comment: Need to set debug="true" in web.config!
By Joseph Craig on
12/22/2010 12:41 PM
|
Re: My DotNetNuke Module Development Environment
Will this work on Windows XP with IIS 5.1 environment? I’m getting erros -
I followed the instructions given in this blog; I use XP. So in step 3 I created a new virtual directory called dnndev and pointed it to C:\websites\dnndev, and did the remaining steps including step 5 (giving ‘Full Control’ permission to localmachine\ASPNET) But when I try to access Installation Wizard using localhost/dnndev/Default.aspx (dnndev didn’t work) it gives the following error:
“Access to the path 'C:\websites\dnndev\web.config' is denied. Your DotNetNuke installation appears to have a security settings problem....”
What am I missing? Any Suggestions/Help greatly appreciated!
Thanks!
By Sam on
1/20/2011 11:51 PM
|
Re: My DotNetNuke Module Development Environment
Sam, you are correct in setting up the directory instead of a web site. You should check to make sure the permissions are propagated down to all files, sometimes XP needs a little massaging to make it do that.
By Chris Hammond on
1/20/2011 11:51 PM
|
Re: My DotNetNuke Module Development Environment
Getting a weird error when I try to start a new project and select the "DotNetNuke C# Compiled Module" as the project type. Error is as follows: "C:\Users\dbyrd\Local\Temp\e5borh5f.zdc\Temp\Wiki.csproj(3,3): The imported project 'C:\Program Files (x86)\MSBuild\MSBuildCommunityTasks\MSBuild.Community.Tasks.Targets' was not found. Confirm that the path in the declaration is correct, and that the file exists on disk." Not sure what to do. I am running my DotNetNuke install directly in VS2010, but I tried starting a new "DotNetNuke C# Compiled Module" project in VS2008, VS2010 (.NET 2.0), VS2010 (.NET 3.5), and VS2010 (.NET 4.0) and none work - they all give me the same error. Can you provide any guidance on how to fix this?
Thanks in advance.
By Dave on
2/2/2011 1:15 PM
|
Re: My DotNetNuke Module Development Environment
Dave, using the latest template you have to install the MSBuild tasks scripts before you can use the templates. The Codeplex page for the Templates provides the info for how to do this.
By Chris Hammond on
2/2/2011 1:16 PM
|
My DotNetNuke Module Development Environment
i'm having a trouble with saving UserDesplay properties when I change start URL to dnndev and use local iis web server to dnndev/desktopmodules/UserDesplay and override application root URL to dnndev/. when i want to save these changes asks me "The local IIS URL localhost/UserDesplay specified for web project UserDesplay has not been configured.to keep these settings you need to configure the virtual directory. would you like to create the virtual directory now?" when i click "yes" then followin error comes up. "unable to create the virtual directory. dnndev/desktopmodules/UserDesplay"
what should i do now. PLEASE HELP me!
By mehrdad on
2/25/2011 9:09 PM
|
Re: My DotNetNuke Module Development Environment
hi
i run web app from my VS under localhost.but if i configure the hosts file placing only 127.0.0.1 dnndev then i think i will have to add another line 127.0.0.1 localhost and add another site in IIS giving host name localhost? is that right way for adding multiple websites to work with?
By Mridul Samadder on
7/4/2011 11:33 PM
|
Re: My DotNetNuke Module Development Environment
So, are you saying I'm SOL since my development environment is Windows XP with IIS 5.1? I can't for the life of me figure out how to configure my machine such that I can access the website via dnndev - I need to type localhost/dnndev. If I change the LMHOST file as you suggest I get prompted for credentials over and over and never get anywhere. Please advise. I have been trying to follow your template tutorial for 3 days now. Thank you!
By Patrick Reddy on
10/7/2011 10:51 AM
|
Re: My DotNetNuke Module Development Environment
I'll try to get an XP configuration tutorial done in the next week.
By Chris Hammond on
7/4/2011 11:33 PM
|
Re: My DotNetNuke Module Development Environment
Hi Chris,
Using(Windows 7+ VWD 2010 express+ sql server 2008 r2 express
I went through template development video. Installed MSBuild.Community.Tasks. The downloaded the "DotNetNuke C# Compiled Module" template and create module.
After build while I am trying to install extension wizard under host and select source zip file it is showing me error as
"Install aborted - The module being installed is not compatible with your host application version ( an upgrade is required )"
Is there any step I am missing ?
Thanks
By Sibabrata Dash on
10/7/2011 10:51 AM
|
Re: My DotNetNuke Module Development Environment
Sibabrata the latest template release requires DotNetNuke 6.0. You can either change the .DNN file to a lower dependency, or upgrade your environment.
By Chris Hammond on
10/7/2011 10:52 AM
|
Re: My DotNetNuke Module Development Environment
Hello Chris,
ENVIRONMENT:
Windows 7 Ultimate 64-bit
Visual Studio 2010 Pro
VB Version of the compiled Templates
After setting everything up according to your blogs and videos, I am having an issue that I can't seem to find a solution to.
When I try to create a module project in VS2010 (or VS2008 for that matter), I receive the following error message from VS:
The local IIS URL dnndev/DesktopModules/MyModule specified for Web project MyModule has not been configured. To keep these settings you need to configure the virtual directory. Would you like to create the virtual directory now?
Here is the section in my vbproj file:
False
True
62597
/
dnndev/DesktopModules/MyModule
True
dnndev/
False
False
False
I tried messing around with different app pools and such to no avail.
By Eric Sutter on
10/19/2011 2:05 PM
|
Re: My DotNetNuke Module Development Environment
Hi I get an error creating the project from template.
The error is:
"The imported project "C:\ProgramFiles/MSBuild\MSBuildCommunityTasks\MSBuild.Community.Tasks.Targets" was not found. Confirm that the path in the declaration is correcr, and that the file esists on disk.!
Can you help me please?
Tnks
By Giuseppe Lucchesi on
11/8/2011 10:35 AM
|
Re: My DotNetNuke Module Development Environment
Giuseppe you need to install the MSBuild CommunityTasks before you can use the template.
By Chris Hammond on
11/8/2011 10:36 AM
|
Re: My DotNetNuke Module Development Environment
Hi Chris,
I have installed dnn under the folder dnndev. While creating a new site in IIS7, I gave my site the port number of 8090. So, I was able to access the dnn website through
localhost:8090/
Now, when I opened VS2008 and did exactly the same steps you mentioned. When I am trying to save the properties of the project after changing to 'Use Local IIS Web server'
I gave the Project URL as 'http://localhost:8090/DesktopModules/moduleExample' and override application root url to 'http://localhost:8090/'
When I am trying to save it I get an error that says
' the url localhost:8090/DesktopModules/moduleExample is not configured in local IIS, would you like to create a virtual directory now? '
When I click 'yes' and reload my dnn home page it says
DotNetNuke Error
and has some details as
'An error has occured. DotNetNuke.Services.Exceptions.PageLoadException:Object Reference not set to an instance of an object - ? System.NullReferenceException: Object reference not set to an instance of an object.............................................'
I am struggling with this thing since a week. I have re-installed DNN for almost 10 times. After reading reviews I thought DNN was one of the best thing to learn to develop websites. I have experience with php and html.
Now setting this is really the most difficult thing.
Please help me...
By subrahmanya kante on
2/5/2012 10:32 PM
|
Re: My DotNetNuke Module Development Environment
subrahmanya please post your question in the Community Exchange portion of our website www.dotnetnuke.com/Community/Community-Exchange.aspx
By Chris Hammond on
2/5/2012 10:33 PM
|
Re: My DotNetNuke Module Development Environment
Hi Chris,
I couldn't get any replies on the community exchange page. I have seen the similar problem which I am facing right now in the comments above on this page. Could you please tell me how to solve this problem. I need to start my work very soon. Now, I am tensed and worried. I cannot find any help on this thing. Please help me.
By subrahmanya kante on
2/7/2012 11:10 AM
|
Re: My DotNetNuke Module Development Environment
subrahmanya, I am sorry, but I would recommend following the steps I provide for setting up your environment, which does not include any ports.
By Chris Hammond on
2/7/2012 11:11 AM
|
|