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.0Creating dll in VS 2005 and creating moduleCreating dll in VS 2005 and creating module
Previous
 
Next
New Post
2/9/2007 12:51 PM
 
Using MS Visual Studio 2005 Professional Edition 8.0.50727.42 I have a module created and working.  I originall had to add the new module definition manually which pointed to the .ascx file.   Now I want to create a installable module (.dnn) that I can send to someone and they can install and get working without.

First off I went to the module and Created Private Assembly which creates the .dnn file.  I put all the App_Code files (2 .vb files), Desktopfiles (.ascx and .vb files) and .dnn file into a zip file.   I then try to add new module using this .zip file and get the following error: 'The 'version' element is invalid - The value '1.0' is invalid according to its datatype 'versionNumber' - The Pattern constraint failed.'

I am wondering if I need to create my codebehind files into a dll instead of using the .vb files.   Not sure how I just create a dll just for these files?   Do I have to basically create a new VS2005 site and can't just add to App_Code and DesktopFiles folder?  Is there a setting in VS2005 that says create dll or not?

Below is how I have setup my files to develop the module.

http://localhost/DotNetNuke_2/
App_Code
 -PR
   -PRP.vb
   -PRP2.vb
DesktopModules
 -PR
  -PRForm.ascx
  -PRForm.ascx.vb
 
New Post
2/9/2007 2:15 PM
 
If you have VS2003 SP1 and you added a WAP (Web Application Project) that would create a DLL for your module project. Check this site out for more information: http://vladan.strigo.net/Default.aspx?tabid=78
 
New Post
2/9/2007 2:17 PM
 

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
2/9/2007 4:03 PM
 
I originally tried the adefwebserver tutorial but when I get to Step 3 my options are different.
Using DNN 4.3.5

Host
 -Module Definitions

Click pencil of module to edit

Dropdown only has 3 options:
-Create Private Assembly
-Help
-Online Help

Below the Control Title | Source section is
Create Private Assembly  (link)

They say to 'select Create Module Package'  I don't have this option.  Mine says, 'Create Private Assembly'.   Is that the same?  Didn't work if so.
 
New Post
2/9/2007 4:28 PM
 
It ended up importing correctly.  The issue was with my version number.   I had 1.1 but needed to be in the format of 01.01.00 and things worked great.
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Creating dll in VS 2005 and creating moduleCreating dll in VS 2005 and creating module


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