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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Problems upgrading my module from dnn3.x to dnn4.xProblems upgrading my module from dnn3.x to dnn4.x
Previous
 
Next
New Post
1/30/2007 7:03 PM
 
Is there yet a solution to this problem?
 
New Post
1/31/2007 4:33 AM
 
I think this problem is solved once I find a way that in PUBLISH (in order for the site to be compiled) I tell VS2005 do not compile global.asax since the the install version of DotNetNuke global.asax is not compiled but distrubuted with its .vb code!!!!
 
New Post
1/31/2007 5:53 AM
 
this issue is happening when i am creating a user control in dnn
 
New Post
1/31/2007 11:04 AM
 
I have spent hours removing parts from my module trying to isolate this issue, and have failed to come up with a solution. Nobody in the DNN core team seems to care about this one so I am forced to deploy my modules with full source code. This of course makes normal installation impossible since you have to edit the web.config file to allow the app_code directory to have C# in there.

This is a real mess and a broken promise as to the way DNN is designed to work, far as I am concerned. I have been looking at Community Server as a platform for new customers. It is very nice, but it isn't designed to be module friendly at all yet.
 
New Post
2/1/2007 4:39 AM
 

Are you using user controls?  Basically if we find a way that when the site is comiled and published (the c:\compiled thing) that if we can instruct the compiler that Global.asax.vb is NOT to be published as compiled but published as code .... then the issue is solved.

This is because in DNN4 global.asax.vb is NOT compiled but is available as a file!

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Problems upgrading my module from dnn3.x to dnn4.xProblems upgrading my module from dnn3.x to dnn4.x


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