Let's do it in french for a change...
Une fois n'est pas coutûme : quelques nouvelles pour les francophones férus d'architecture.
La parution de septembre du magazine Programmez présente le métier d'architecte logiciel, notamment à l'aide de l'avis d'acteurs du domaine. Dépêchez-vous car le numéro d'octobre arrive...
Deux conférences/symposiums/séminaires gratuits à ne pas manquer :
- Le symposium DotNetGuru du 9 octobre. (un peu tard pour s'inscrire, désolé)
- CTO's Days du 18 novembre proposé par BrainSonic : Modélisation et Architecture au coeur des systèmes d'information.
The WinForms debate on Chris Frazier's weblog and mine showing some heat-up generated many comments. The most interesting comments are those showing that the WinForm team is listening: among the comments you'll find replies from Brian Pepin.
For Windows XP: http://support.microsoft.com/?kbid=314056
Here are some recent articles about CodeSmith:
Article on Tech Head Brothers about CodeSmith (In French)
I'm currently working with Winforms for a project, while my background on .NET is mostly web apps.
I won't be as severe as Christopher Frazier, but I too am disappointed with the windows forms. Winforms don't work at all like webforms. I knew beforehand that webforms and winforms were not close in design, but this reality strikes me now that I have to work with winforms.
Also, when working with winforms, it's not long before bugs or rough aspects appear. The DataGrid control is a good example of this.
Like Christopher, I'd like to drop a "note to the windows forms team": Microsoft tells us to build smart applications, mixing winforms and web technologies. I think it's good, we need this. But you have to help us, bring winforms and webforms closer!
Martin Spedding presents the onion approach as a way to mask complexity of development platforms to achieve simplicity without losing power when needed.
The problem I think is that in many ways what people really want is an "onion approach" to development. Very simple to start off with but one that provides immediate response and uses a simple syntax. However, one that grows with you, so that each time you remove another skin of the onion the complexity may increase but so does your flexibility.
I agree on the onion approach and the PDC.
Of course, .NET gets more and more powerful everyday, but this comes with increased complexity. I think a good way to hide the complexity (without losing the richness of the platform) is to use higher level frameworks. Those frameworks need to be oriented and dedicated to specific media and businesses (web, winform, content management, ...). They also need to be open enough to let the power developers dig deeper and take full advantage of the whole .NET platform.
Note: Surely enough, this does not apply to .NET only.
Using a checklist for this is an excellent way to make sure nothing is forgotten.
Now, who wants to create the tool that would validate this set of rules, please? ;-) (/me think FxCop like...)
If you've worked with the Int32, DateTime, Decimal types in C#, you probably faced a little problem one day: these data types don't support the null value.
Stop grumbling! Don't search further, the solution exists : http://nullabletypes.sourceforge.net/
PS : If you never worked with the Int32, DateTime or Decimal types... you never used C#!!! ;-)
A new realease of the DAAB is available. This version offers support for ADO.NET generic interfaces.
I need to check this out to see how they did it, see if we can use it, and compare it to what we did.
IBM and Microsoft give a progress report on web services and associated specifications:
One of the most useful articles about WS, ever.
Check this out, definitely. Recommended.
The SharpToolbox now contains... 292 tools! And more are in the pipe waiting to be added...
Pour nos lecteurs francophiles, un dossier spécial sur .NET dans 01 Informatique : .Net trois ans après : l'offre grossit, la demande s'amorce.
Funny post by Roy, just read it.
I had to give it a try. So now I know who I am :-)
Your Type is
Introverted Intuitive Thinking Perceiving Strength of the preferences % 33 44 44 33 Qualitative analysis of your type formula
- moderately expressed introvert
- moderately expressed intuitive personality
- moderately expressed thinking personality
- moderately expressed perceiving personality
Of course I knew I am a moderate person :-)
Please call me Mister Architect!
- moderately expressed introvert
Why is the simple concept of rooms the size of a small team often neglected?
Why is everybody after cubicles or open spaces?
Having relatively small rooms (4 to 7 people) seems simple and efficient enouh for me. One size does not fit all. It depends on your business and the size of your team.
Jonathan Cogley says why he is not a fan of cubes. I would hate having to work in a cubicle for the reasons Jonathan highlights. An open space has almost as many disavantages as cubicles:
- Of course you have no privacy at all, so you cannot feel "at home"
- You can easily get disturbed by anyone speaking or walking or dancing or whatever the fool decides to do in the room to help you loose (lose!) your focus
- You cannot ask help from you teamates because you have to keep quiet in order not to disturb the others
- You feel less part of a team compared to a small room where only people focused on the same project or technology are with you. You just feel like being part of a big thing. That can be motivating, I recon. But being surrounded by highly motivated teamates is better, IMO
Of course walls everywhere is not good for productivity. But why choose the extremes?!
Idea: a web service aggregating RSS feeds the way any RSS client does, plus a light WebForm frontend for interaction. One of the goals is being able to retrieve the content of complete RSS feeds without missing posts just because your client-side RSS aggregator is down. This is similar to what Jesse Ezell did with the .NET Weblogs archive but as a WS and with more options to come. A somewhat similar product is the Genecast News Service which converts RSS feeds into Usenet news feeds. See also Bloglines and MyWireService and Feed-Me.Info and SyndiCache and MyBlogroll.
Such a server aggregator should be used with clients, so an API needs to be defined. Maybe Atom brings something new compared to RSS on this matter. I didn't have time to check it out.
I'm thinking about three interfaces:
Admin (password protected, SOAP only)
User (password protected, SOAP only)
- void FlagFeedItems(string feedID, string itemIDs, bool setFlag)
- void MarkFeedItemsAsRead(string feedID, string itemIDs, bool beenRead)
- XmlDocument SearchInReadItems(string query, [optional] string feedID)
General (free for all)
- XmlDocument ListFeeds() [HTTP GET + SOAP, returns OPML]
- Feed.Properties GetFeedPropertie(string feedID)
- XmlDocument GetFeedContent(string feedID, int maxItemCount) [HTTP GET + SOAP, returns RSS]
- XmlDocument GetFeedContentByDate(DateTime minDate, DateTime maxDate, int maxItemCount) [HTTP GET + SOAP, returns RSS]
- XmlDocument GetFeedInfo(string feedID)
- void SubmitRssFeed(string url)
- XmlDocument Search(string query, [optional] string feedID)
I already have some pieces of source code, but this project is a bit stalled at the moment due to lack of time. If someone is interested in seeing it, just let me know.
See also my suggestions for MyBlogroll.
Update: this is somewhat related.
Paschal L points to a good ressource:
Why don't we have a "previous stuff" link at the bottom of weblog pages which would give access to the n previous posts?
Is this against the weblogs religion?