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

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationMaking AD Provider work with ADAMMaking AD Provider work with ADAM
Previous
 
Next
New Post
9/15/2008 1:51 PM
 

Ok, now we want to make the sketched changes ourselves against the latest release. However I am new to DNN development. How do I set up the config around the source project to compile?

The situation in more detail:

OS Vista, Development environment VS2008 with SP1.

-I have set up DNN 4.8.4 source package (4.9.0 also works). It compiles and I can login in the site on http://localhost/dotnetnuke_2(After setting trust to full).

-Now when opening the solution for the AD provider It suggests to make a virtual directory to the source of the AD provider. I allow it to make one in IIS.

-This virtual directory(application on IIS7)  get's made and points to the correct directory.

However the source does not compile. Now I feel stupid. What am I doing wrong?

 

 

 
New Post
9/15/2008 9:03 PM
 

Hans, you really don't need to have the DNN source to work with the AD provider (though it helps if you're going to have to debug the actual DNN source code). You should be able to just edit the .2008proj file in notepad to point to your DNN install and then launch the 2008.sln file (you'll need to have MSBuild.targets installed on your dev machine). I'm on my way out the door for a few hours but if it's not too late when I get home I'll try to post a step-by-step of what you need to do.

 
New Post
9/16/2008 1:38 AM
 

Hans,

Open the .VS2008.vbproj file in Notepad and go down the the botttom of the file. Look for the line

<IISUrl>http://localhost/Dotnetnuke_2/DesktopModules/AuthenticationServices/ActiveDirectory</IISUrl>
and the line
<IISAppRootUrl>http://localhost/Dotnetnuke_2</IISAppRootUrl>
. Change Dotnetnuke_2 to match the url of your development site. Then close and save the file.


Also open the DNNModule.targets file in Notepad and change

<EnableDeployment>1</EnableDeployment>
to
<EnableDeployment>0</EnableDeployment>
. That will stop it from building an install/source package every time you build the project.

Then launch the project by double clicking on the .vs2008.sln file or by opening it through VS2008. Go to the Properties of the project and click on the Web tab. Make sure the URLs are correct. If you want to launch the website out of VS2008 (which works better than attaching to it when you're working with an authentication provider) you'll have to click on the radio button "Start URL" and type in the URL for your development site.

That should do it I think. Let me know if you run into any problems.

 
New Post
9/16/2008 5:01 AM
 

with some struggeling I got it compiling and even let it generate deployment zips.

But I still have some questions.

First of all I initially unzipped the SourceFiles.resources "zip" into its own directory instead in the directory that is containing SourceFiles.resources. Is the way Did the right way?

Second, I am missing References to the DotNetNuke.dll and the DotNetNuke.Membership.DataProvider.dll. I set these in Visual studio but that is probably not they way it should be done. Can you please tell where I should  configure these?

Third when using packaging, the dir D:\temp\packaging\packagetemp is required. The last part of the path, packagetemp, is not automatically created. Is this a bug?

Finnaly, I am now having a virtual Directory mapped in my DNN install. How do I let DNN know that it can use my modified Active Directory Provider?

 

 
New Post
9/17/2008 12:40 AM
 

Hans C.J. Kruse wrote
 

First of all I initially unzipped the SourceFiles.resources "zip" into its own directory instead in the directory that is containing SourceFiles.resources. Is the way Did the right way?

They should be unzipped into the directory containing the .resources file and not their own (i.e. They should be in the DesktopModules/AuthenticationServices/ActiveDirectory directory).

Second, I am missing References to the DotNetNuke.dll and the DotNetNuke.Membership.DataProvider.dll. I set these in Visual studio but that is probably not they way it should be done. Can you please tell where I should  configure these?

If you "Show All Files" in VS 2008 and add them under references then that's all you need to do. I've found that references being missing is fairly common in Web applications as almost everyone installs the source application to a different location.

Third when using packaging, the dir D:\temp\packaging\packagetemp is required. The last part of the path, packagetemp, is not automatically created. Is this a bug?

I'll have to look at it. I haven't had any problems getting the packages built so I'm not overly worried about it.

Finnaly, I am now having a virtual Directory mapped in my DNN install. How do I let DNN know that it can use my modified Active Directory Provider?

Is your provider using the same directory etc. that the original was installed to? When you build your project it should be replacing the .dll in the bin\Providers directory of your DNN Install and, that being so, will automatically use your changes.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationMaking AD Provider work with ADAMMaking AD Provider work with ADAM


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