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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Namespace / Assembly .dll ISSUENamespace / Assembly .dll ISSUE
Previous
 
Next
New Post
5/29/2008 5:33 AM
 

Hey

 

I just bought a new module + source which im trying to configure. Now it comes with all the .ascx , .vb files etc. I have added them into a new module in a new website in Visual Studio. Here is my problem which I cant seem to get around:

 

In the install directory is a .dll for the module. (I dont see why I would need this as I have the source and would only be compiling .dll files later on?) Anyways, if i dont add it under my bin directory, it gives me errors for every .ascx file "Could Not Create Type:" blah blah, the same error as when your namespace is wrong. I have double and triple checked that my .ascx INHERITS property is set correctly, and also that the .VB file has the same namespace and also file name etc. I even tried changing namespaces with no luck

<%@ Control language="vb" Inherits="DotNetNuke.jb_ClassifiedsSearch" CodeBehind="jb_ClassifiedsSearch.ascx.vb" AutoEventWireup="false" Explicit="True" %>

Namespace DotNetNuke

    Public MustInherit Class jb_ClassifiedsSearch

 

Now, as soon as I add this .dll into the bin folder, these namespace issues dissapear. but now a NEW error appears. Many methods are now being detected as ambigious (Prolly cause its detecting the methods in the .dll AND the source code files) However, I cant access these methods, when I try DotNetNuke.jb_Utility. for example. I try be specific and call the methods from the actual source code, but its not picking it up. Almost like a conflict.

 

Any ideas?

Do I need the .dll in the first place?

Why is it when I change the namespace from DotNetNuke (the way it came) to for example 'AA' it doest work. Like the namespace is wrong, yet I know ive typed it in correctly. Are these source files somehow dependant on the .dll?

 

 
New Post
5/29/2008 9:27 AM
 

Hey Chris,

Sound for starters like the module you have obtained is setup as a WAP project. 
Have a look at the various help guides on this site for guidance in how to setup
a development environment for WAP.

http://www.adefwebserver.com/DotNetNukeHELP/DNN4_WAP/  may be a good place to start.

But regardless - does the module source code include a VS solution. .sln or .proj file.
If it does your best bet is to open this solution to do any work on the module.

Second question - what version of DNN is the source code designed for - if its DNN 2.0 then you may
do so some work to get the module converted to be compatible with DNN 4.8.3

Westa

 
New Post
5/29/2008 11:45 AM
 

I struggled and struggled with this problem ALL day and finally found a solution. I change in my aspx files the value CODEBEHIND to CODEFILE and that fixed the issue. Something so stupid. I thought they were both the same command. obviously not. And if CODEBEHIND doesnt work, why is it even included in VS 2008 :(

 

Thanks for the helps anyways

 
New Post
5/29/2008 10:39 PM
 

vs2008 and the newer versions of dotnet use a code beside methodology and partial classes
 - which is different and much cleaner way of workoing than the older 1.1 code behind process.

Westa

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Namespace / Assembly .dll ISSUENamespace / Assembly .dll ISSUE


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