Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Apr 19, 2007 07:36 PM by steve harman
Mar 07, 2007 04:39 PM|LINK
Microsoft has generously offered to “hand over the keys” to these CSS Friendly adapters. To be clear: Microsoft has approved the idea of directly letting the community decide on and implement changes to the ASP.NET 2.0 CSS Friendly Control Adapters.
Personally, I think this is great
Thanks to Brian Demarzo, we have a project already set up at CodePlex,
http://www.codeplex.com/cssfriendly. However, I think Brian’s intent was focused towards offered the community a specific packaging option: putting all of the adapter code into a single DLL. A community-wide CodePlex project for these adapters would have
a broader goal, I suppose. Perhaps we can morph Brian’s project, with his permission, of course, into something that more people can contribute to. Or, we can agree to start fresh with a new CodePlex project.
What are your thoughts?
Mar 07, 2007 05:38 PM|LINK
Russ, I think this is GREAT. I think we could easily combine the 'stand-alone' version of the adapters with the adapters themselves. In a sense you can even combine them -- I'm sure in time many people will be very happy dropping a DLL that adds functionality
rather than adding a bunch of CS files.
As an aside, I actually integrated a community-provided fix to a CSS adapters bug in my code base, but I didn't check it in to CodePlex yet. (The fix was from here:
I think the best solution is the morphing one -- there should be "one" CSS Friendly project, not multiple ones. Either both can be combined and the "standard method of distribution" would be the precompiled DLL but with source code available (similar to
the Ajax extenders), or the precompiled version can simply be an alternate method of doing the same. I'm actually a fan of the former, and not out of ownership reasons, but because I would think that most people who use the CSS adapter code don't modify the
code files -- and if they did, they should contribute their improvements to the shared source project.
Mar 07, 2007 05:44 PM|LINK
Mar 07, 2007 05:50 PM|LINK
I'm glad we're on the same page.
The first order of business may be to finalize the approach and get the code organized in a way to make it work. For example, if we're leaning on the project being a library of functionality that can be dropped in to a web site (i.e. the precompiled CSSFriendly.dll)
the forums and get things working.
It would be interesting if anyone had thoughts on how we can unit test these adapters. I'm not too well-versed in TDD (especially for web applications), so if anyone has suggestions, it would be great to hear them.
Mar 07, 2007 06:48 PM|LINK
Hi! I think the idea is great!
I'm using the adapters since the early versions and I'll love to see this project going on.
Mar 07, 2007 08:42 PM|LINK
Mar 07, 2007 08:49 PM|LINK
Mar 07, 2007 09:01 PM|LINK
Mar 07, 2007 09:14 PM|LINK
I program in VB, I prefer it above C#, but I believe that C# is the choice of most developers here. And I strongly agree that only ONE version of everything should be done.
For these reasons, and also considering that the key people involved, like you, prefer C#, I think that the question is answered! :):)
Mar 07, 2007 09:32 PM|LINK