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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesHow To Create A PA Module from a VS2008 Source Project Using 5.2.3?How To Create A PA Module from a VS2008 Source Project Using 5.2.3?
Previous
 
Next
New Post
4/1/2010 5:25 PM
 
Nick,

The solution I described does not have any bareness on whether it has web services or it’s size. Based on you development pattern you will need to assemble all of your code into a dll assembly to ship it as a PA.

Being the size of your project this could probably be done in as little as 30 minutes.

1 ) Open VS and select “File > New Project” Select your language type and Class Library from Templates.

2 ) Copy ALL of your vb code from the APP_Code/MyModule and DesktopModules/MyModule directories to the root of the project created in step 1

3 ) Right click on the class library project “Add > Exiting Items”, and add ALL of the files you copied in step 3

4 ) Open the My Project Page and select References and add the DotNetNuke.dll and any other dependency that may be required.

5 ) IF there are controls (textboxes, ddl, ect) add these to each vb file. Example “Protected WithEvents txtMyTextbox As System.Web.UI.WebControls.TextBox”

6 ) When all reference errors are resolved build the dll

7 ) Open all the ascx/aspx files and replace CodeFile with CodeBehind

8 ) Package you DNN install



Robert Harriman
WEBMAZING.NET
AutoWebSuite / BrokerWebSuite

DNN Modules for Auto Dealers and Real Estate Professionals.

 
New Post
4/1/2010 5:32 PM
 
Chris,

I disagree with assuming that WAP is the solution for every situation. For example, I have several hundred custom modifications of the extensions I ship, almost all of them are minor in scope with two or three files being affected; if I were to maintain this scenario in WAP, I would have have hundreds of custom solutions while requiring my third party integrators/clients to perform more steps in the modification process and forcing them out of VWD option. Moreover it would be an outright nightmare maintaining upgrades – having to merge code into the solutions and packaging them for the DNN install, instead I can have one install package and replace the modified files as necessary. The overhead to this is maintaining the class library for PA installs but once the setup is done it isn’t that time consuming.

A little off topic, I am located about 100 miles from you and have every intention in attending some your user group meetings, do you plan on having them monthly or a email list I can subscribe to.



Robert Harriman
WEBMAZING.NET
AutoWebSuite / BrokerWebSuite

DNN Modules for Auto Dealers and Real Estate Professionals.

 
New Post
4/3/2010 5:05 PM
 

Robert - that is great and worked a treat. Many thanks.

One thing slightly puzzles me though and that is if you have only a few minor changes why not simply release  a new dll and the (modified) ascx's  ?

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesHow To Create A PA Module from a VS2008 Source Project Using 5.2.3?How To Create A PA Module from a VS2008 Source Project Using 5.2.3?


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