From Husein Choroomi: The programming language C#, as well as the CLI (Common Language Infrastructure), have passed through a working group within the ISO (International Organization for Standardization) and will likely be approved by January, said John Montgomery, group product manager with Microsoft's .Net developer platform group.
From Keith Wedinger: Microsoft and its allies have quietly expanded an effort to gain acceptance for C#, the software giant's competitor to Java and a foundation for its next-generation Internet services.
"SQL Server Centric .NET Code Generator (code named OlyMars) is both a flexible and powerful code generator based on database modeling. It allows instant generation of both SQL and .Net code providing a complete library of stored procedures, .NET classes and ready-to-use Windows/Web form controls (including associated documentation). SQL Server Centric .NET Code Generator is also fully extensible to use one's own custom templates and consequently can be adjusted to generate any custom code respecting a homogeneous implementation scheme within the company (can be written either in VB .NET or C# .NET)."
This isn't particularly new, but it's new to me and it's from Microsoft France. I also saw that Justin Rudd has used it. Can anyone contribute any comments about OlyMars?
[pinetree-tech.com/weblog]
"Many developers will be surprised to learn that SOAP isn't the only game in town for Web services interfacing. REST offers a perfectly good solution for the majority of implementations, with greater flexibility and lower overhead. Developers need to stop reaching immediately for SOAP and start choosing the right technology for the application."
I thought that this article would be an interesting counter-point to Peter Drayton's "Designing a RESTful SOAP API" at the DevCon this week.
"With current versions of Outlook, losing a network connection or working with a slow or unreliable network connection produces horrible results. If Outlook loses its network connectivity, error messages pop up before Outlook freezes completely. Outlook 11 eliminates this problem. Details have not been fully released, but Outlook 11 will work in what is termed "cached Exchange mode." When a fat pipe (a high-speed network connection) is present, Outlook will run much like it does now, where headers and message bodies will be downloaded as new messages arrive. When Outlook detects a slower pipe, either a dial-up or a cellular modem connection, only message headers will be downloaded. If a user wants to display a message, the entire message body will then be downloaded from the server. Outlook's default behavior will be to work against its local cache."
Now this sounds more like it!
"MEC 2002 opened yesterday morning with a keynote address by Paul Flessner, senior vice president of .NET Enterprise Servers, that was packed with product announcements, demonstrations, and promises for the future."
Apparently, Microsoft thinks that .NET Server's support for Volume Shadow Copy (VSS) Virtual Disk Service (VDS) are both really cool. Mr. Fetcher also demo'd the simply amazing ability of Outlook 11 to show the preview pane to the right of the list of emails instead of at the bottom. Myself, I'd be really happy if Outlook had zero new features, but included responsive multi-threading code.
One thing that does sound interesting is "Greenwich" which is supposed to be an intranet, secure platform for doing IM. If I can use MSN IM to connect to internal and external IM accounts simultaneously, that'd be pretty darn cool.
