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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Open Source of a Closed SystemOpen Source of a Closed System
Previous
 
Next
New Post
5/6/2006 4:27 AM
 
Let's talk about it.
I'm working on it. I found that quite every module that use File System use to join directory with "\" character instead of using System.IO.Path.DirectorySeparatorChar that is the way DotNet gives to write system independent applications. Code is full of Replace("/","\") and similar stuff.
I've tried to substitute some hardcodeded backslash, I've modified Global.asax.vb, Globals.vb, and a lot of files, and it seems that something works, but:
- it's a dirty work (but someone got to do it)
- it's useless if is done outside DNN core team: I'm working on 3.2.2 source, but 3.3 will overwrite my modifies. don't talk about 4.x

Now, I think that:
- linux/mac/bsd compatibility for DNN would be a great plus and DNN core team should be involved
- work for compatibility should be approved and incorporated in DNN core
- I'll work for it anyway because we need it
- I'd like to coordinate a common solution: I see at least 3/4 main way tosolve the problem.


btw: I'm looking for a mod_mono hosting solution, better if in Italy
 
New Post
5/8/2006 8:59 AM
 
Unfortunately, neither of us are in the CT. To get this integrated, we need someone to champion it who has access to the core code.

The problem of hard-coded strings is ridiculous and it's all over the place. I hate that, but the task would be huuuuuge and, like I said before, I don't have access to the core to even work on it every once in a while.

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
5/8/2006 9:41 AM
 
Is there anybody in the core team interested ?
 
New Post
5/8/2006 1:34 PM
 

I would say there are plenty of us interested, whether or not anyone has the time, or it best serves the needs of the community is a different matter. At the minute we're focussed on the next release, so I doubt anyone has the spare cycles to look into this further at present. I'd be happy to table it as an item for the next time we are scoping a future release, and see if someone will take it on or mentor an effort. Of course, to advance it you could do the investigation and send a proposal through to the coreteam - it is an opensource project after all :)

The one qualm I would have is that Mono (at present) only supports asp.net 1.1, so I'd like to see a stable 2.0 version as the majority of our users and efforts are heading that way.

BTW, some of the odd \ to / conversions are remnants of prior code that was used by friendlyurl's I think. As such, we'll be refactoring and removing it.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
5/8/2006 7:09 PM
 
As I said before, I'm going to work on it. I'd like not to wast time and find that all the work must be thrown away because DNN changed. I'm not looking for help (but if someone wants..), I' d like to do something useful. I've already wasted time porting membership provider to MySQL and you rewrote it. So, I'd like:
- someone to fix a strategy
- a preview of next release code
I'm now facing to mono Basic compiler limits: how much can be translated to c#

thanks
cristian

c dot vanti at tin dot it
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Open Source of a Closed SystemOpen Source of a Closed System


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