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

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Injecting MenuInjecting Menu's As Skin Objects
Previous
 
Next
New Post
8/17/2006 2:44 PM
 
Happy you solved your problem.
I think you are completely right about browser detection in 1.1
It feels as if it's half finished.....
 
New Post
8/23/2006 3:20 PM
 

Agreed!

It seems that the intention of MS to support all the products out on the market was too poorly conceived. I think that the .NET team under estimated the sheer number of devices out there and never really addressed it in 1.x. They decided to revamp it and deploy it with Whidby instead. All in all, I'de say it was a good idea to roll it out in 2.0 rather than complicate 1.x with another service pack. Now a new device is just an additional config file. and all up to the machine config... No more hassles with the actual web applications themselves (aside from developing within the confines of the compact framework anyway).

 

 


Cheers!
John Valentine
http://www.webinnovationsystems.com
 
New Post
8/23/2006 7:39 PM
 
I read somewhere they left the updating of the machine.config for .NET 1 to a company called Cyscape.com, but since they are also marketing their own software for browser detection, nothing happened.....

Read more here
 
New Post
8/24/2006 9:09 AM
 

You know that wouldn't suprise me at all. Microsoft has a tendency to subcontract many of the "secondary functionality" pieces out to "experts" in the field for most of their solutions. From my own experience, it almost never works out for the best possible solution.


Cheers!
John Valentine
http://www.webinnovationsystems.com
 
New Post
8/24/2006 9:39 AM
 

This is the exact reason I decided to implement the spmenucaps.config (solpart) and the ClientAPICaps.config (DNN Controls) files.  There is no ruling authority on the browsercaps section.  See page 11 and 12 of this doc for details on editing these files.  The basic flow behind detection is like this

Browser sends UserAgent -> browsercaps (machine.config) -> ClientAPICaps.config/SPMenuCaps.config -> WebControl Rendering

The ClientAPICaps.config file can be found in the js folder.   The SPMenuCaps.config is found in controls\solpartmenu folder.

These files work for both .NET 1.x and 2.x Frameworks.


 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Injecting MenuInjecting Menu's As Skin Objects


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