Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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.0Rescue a Visual Studio 2003 DNN installationRescue a Visual Studio 2003 DNN installation
Previous
 
Next
New Post
5/8/2009 4:24 AM
 
Pyabo

Joined: 4/8/2009
Posts: 12

I've inherited a DotNetNuke project that I need to make a number of changes to... Luckily the upgrade to 4.9.3 went smoothly.  Now I need to update some of its custom modules. 

Unfortunately, all the .sln and .vbproj files that came with it seem to be in an old VS format.  I believe it's VS 2003 or somesuch.   The conversion wizard absolutely FAILS to do anything useful... the solution opens, but half the files (all the code behinds) are missing... the main DotNetNuke project is missing... files are moved to places they shouldn't be... etc.  How do I rescue this project?  Am I going to have to go through and recreate every solution and project file by hand?  I'm not even sure where to begin there!

Can I recreate or build just the custom modules in some other (sane) DNN installation?  I have a clean source project I downloaded and set up that seems to work OK.

Advice?  Prayers?
 
New Post
5/8/2009 5:52 AM
 
Erik van Ballegoij


Erik van Ballegoij's Avatar

erikvanballegoij.com
Joined: 4/7/2004
Posts: 4445

you should not touch the main dotnetnuke project anyway (core changes will be lost if you upgrade again)

Custom modules can have their own project files and solution files, IF they are WAP modules (compiled modules). In such case, you NEED the source files of the module in order to make changes to them. WSP modules are not compiled and always come with full source. You can edit those by just opening the website in visual studio

Also then: you must be carefull not to touch modules you bought (unless you know what you are doing)... because then if you install an upgrade of the module, you will loose your changes

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn
 
New Post
5/8/2009 6:06 PM
 
Pyabo

Joined: 4/8/2009
Posts: 12

OK... I guess the next question then is... How do I add a WAP module?  All of the getting started guides and tutorials I've seen assume a web site.  If I add a new WAP, what are the requirements?  Do I just add a reference to website\bin\DotNetNuke.dll to get all the DNN-specific support?

I got this module I'm working on to compile last night by dropping into my DNN source site, and changing Codebehind= to CodeFile=... but then of course I don't get a separate DLL for it.
 
New Post
5/9/2009 4:55 AM
 
Pyabo

Joined: 4/8/2009
Posts: 12

Of course, shortly after I posted this I discovered the Compiled Module project template.

Unfortunately, it always throws an exception when I try to use it in VS 2005.  :(
 
 Page 1 of 1
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Rescue a Visual Studio 2003 DNN installationRescue a Visual Studio 2003 DNN installation


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