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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installation with SolutionInstallation with Solution
Previous
 
Next
New Post
10/4/2006 11:28 AM
 
I am trying to do something that was easy to do in the 3.x versions, but has become rather difficult for me to figure out now.

I am following the installation instructions with the Virtual directory, etc. And I get the website up and running fine. No problems.

The next thing I want to do is compile in a custom skin object that I wrote in 3.x. I did this basically by copying another skin object, changing what I needed, and compiling the main solution in the root directory of 3.x. Worked like a charm.

The problems I am running into in 4.x are:

1. The solution file in the root of the source install includes the website, and builds cleanly. But doesn't actually ever seem to really "Build" the website. Any changes I make to the .ascx file I created don't seem to take, even changes I make to the existing skin objects don't error, but don't seem to compile either. I did go into properties and noticed that the solution has the build option unchecked, but even checking that makes no difference.

2. When trying to do step through debugging, I get the message stating that my breakpoints won't be hit because no symbols are loaded for the project.

I am hoping I am missing something basic, otherwise I can tuck my tail and head back down to 3.x versions for this project, I just had high hopes of finally upgrading to 4.0.
 
New Post
10/4/2006 4:40 PM
 
Allot of testing, and testing again I figured this out. In general for those having compilation problems:

1. Set the name of the website you are doing your testing on in the solution file using a text editor.

2. Make sure toe check that the "site" in the solution is set to debug in both the web.config and the configuration options.

3. Do a "Rebuild" of the project intially, this gets rid of allot of not registered, wrong version, etc issues I was having and gets everything synced up.

4. After all of that is done, a very suttle change has been made in ASP.NET 2.0 that I missed. In the register tag, CodeBehind is now CodeFile (thank you Microsoft).

Everything is working fine now, I still can't do step through debugging, but being able to successfully compile is enough to keep me going on this one.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installation with SolutionInstallation with Solution


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