Learn More





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 ExtensionsModulesModulesDebug and Packaging problem with moduleDebug and Packaging problem with module
New Post
6/3/2014 9:53 AM

I have a module I've been converting to DNN7 from DNN4, and from VB to C#. It's a multi-part module, with some components shared between the parts.

There are a few strange things that have been happening. First off the old VB would not work when recompiled until I manually build the .designer files and moved some declarations. I used SharpDevelop to convert each to C#, and have done some restructuring to prepare for more DNN7 "like" behavior. So far so good, I have the module with both components working fine locally. I haven't tackled the "fancier" stuff like iPortable or iSearchable yet, just trying to get all the views and links working, with some basic CRUD operations.

Now comes the really weird part. I've been converting a page at a time, and all the various list views and cross links work fine. I converted a pair of view and edit pages, but I cannot step through them in the debugger. I can put a breakpoint in the DAL and hit that, which is called from the view or edit page, but I never hit a breakpoint in ascx.cs itself. I can hit them in the first pages I converted, but not the recent additions. The pages in both packages work fine LOCALLY, and when I run the install package wizard on the production site it works fine too. All the list pages in the first package work fine, the 2nd package doesn't work. The detail view/edit pages (the ones that won't debug) display an error that the ascx.cs is not found (which is true, it's not in the installer, but neither are the pages that work).

I'm totally baffled as to how to proceed. I've done cleans, builds, rebuilds, looked manually at the project file to compare the working and non-working pages, etc. It seems like both a DNN packaging problem AND a build problem, but I can't explain why it works locally just fine if it's a build problem.

New Post
6/3/2014 2:16 PM
My guess is that the original files were created as code files using the Website model but now you are using the Web Application Project model with code behind files and designer files.

In Visual Studio - right click on the project node in Solution Explorer - and if there is a "Convert to Web Application Project" menu command execute to fix the files.

Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
ASPInsiders Member
View my profile on LinkedIn
New Post
6/4/2014 11:56 AM

That was it! Sure enough, no matter how long I looked at it I didn't see it. The detailed view/edit were generated by DNNKickStart, and had the codefile directive instead of all the others with codebehind. Changing that fixed both the debug and packaging problems! Thanks much.

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDebug and Packaging problem with moduleDebug and Packaging problem with 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.
Try Evoq
For Free
Start Free Trial
a Demo
See Evoq Live
Need More Information?