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
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...skin proble in asp.net 2.0skin proble in asp.net 2.0
Previous
 
Next
New Post
5/9/2006 1:25 PM
 
Erik van Ballegoij


Erik van Ballegoij's Avatar

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

For now i fixed it by changing the assembly version of my dev dnn environment to 3.2.2.0, so without build number. That will cause the version number in my module's references to be also 3.2.2.0, which will be always lower than the actual version.

I sent softsoap a new version by mail, if it's working for him, i will put out the update to all channels....

cheers,

Erik

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

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn
 
New Post
5/9/2006 3:36 PM
 
John Mitchell


www.snapsis.com
Joined: 4/18/2003
Posts: 3987

 

Hi Erik,

I didn't realize it was your skinobject, I just read the error and I must have misinterpreted it.

So the module was compiled using a version of DNN as a project reference?

If so, then that must be the issue, although I'm as surprised as you are that this does not work in ASP.Net 2.0.  
Maybe it has something to do with dynamic compilation.  Is the source file included with the skin object?

I'll see if I can recreate this problem, but if you figure out a solution in the mean-time I'm all ears.

DotNetNuke Modules from Snapsis.com
 
New Post
5/9/2006 3:42 PM
 
John Mitchell


www.snapsis.com
Joined: 4/18/2003
Posts: 3987

 

And now I see that you did already post the solution which makes sense.

So it was actually that the version of DNN you compiled against and referenced was newer than the current release because your version was being compiled each time.

I believe we had ran into this problem on the core now that my memory has been refreshed and took those last version numbers out as well.

 

 

DotNetNuke Modules from Snapsis.com
 
New Post
5/9/2006 3:49 PM
 
Erik van Ballegoij


Erik van Ballegoij's Avatar

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

John,

Its a quick and dirty fix, i have no real experience in creating dnn 4/asp.net 2.0 modules, so it could be that this problem will fade away. However, if we keep this problem with native dnn 4/asp.net 2 modules, maybe its a good idea to remove the build number from the assembly version for release builds... and maybe alltogether... Do you guys use the build numbers internally for any reason at all?

Cheers,

Erik

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

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn
 
New Post
5/9/2006 3:59 PM
 
John Mitchell


www.snapsis.com
Joined: 4/18/2003
Posts: 3987

 

No, we don't use it that I know of.

I thought we had taken it out, but I just got the latest code and it's still there, so I'll ask why.

DotNetNuke Modules from Snapsis.com
 
 Page 3 of 4
Previous1234Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...skin proble in asp.net 2.0skin proble in asp.net 2.0


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