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.