Microsoft Corporate VP S. “Soma” Somasegar has the news at his weblog:
Today, I’m pleased to announce the availability of the beta of Visual Studio 2005 Service Pack 1.
Based on your feedback, Visual Studio 2005 Service Pack 1 addresses issues that were found through a combination of customer reports, MSDN Product Feedback Center and internal testing. I know that this Service Pack is a little late in coming. While I regret that it took longer, we wanted to be as thorough as possible about taking your feedback and decided to take the extra time. You can find a technical description of some of the fixes included in this service pack and download the beta by registering on the Microsoft Connect Site. We’ll have the complete list of fixes posted when the service pack releases. Pending feedback from you on this beta, our plan is to ship the final version in the next 3-4 months.
Also of interest was what was revealed about tool support on Vista. Hit the link for all the details but the net is:
I’d laugh about the last item except that whenever I need to whip up a quick client (as opposed to Web) application, I invariably reach for VB6.
The first “beta” was a Community Technology Preview in May, but now Expression Web Designer (AKA Quartz) has arrived as a full fledged Beta 1 with a name change as Microsoft CVP S. “Soma” Somasegar recounts at his weblog yesterday:
Earlier today, the team signed off on Beta1 for Expression Web (formerly known as Expression Web Designer) which provides you with a rich set of tools to build high quality, standards-based web sites.
You can download this beta from Expression Web and send us any feedback that you have on this.
The beta requires the .NET 2.0 framework before you can play.
One, the WYSIWYG web design software no longer supports the creation of FrontPage files. And two, Microsoft is changing the name from the incredibly boring “Expression Web Designer” to the incredibly opaque “Expression Web.”
Regarding the removal of FrontPage support, product manager Wayne Smith said MS has “removed from the product is all the entry points that allow people to create new things with FrontPage tech. But the editing tools remain.”
You can still render FrontPage pages and edit them, but there are no mechanisms to create new FrontPage instances.
That may be OK, but as I mentioned previously, while FrontPage got no respect, it continues to be ubiquitous in both Windows and non-Windows Web hosting.
IronPython is a Microsoft sponsored open source implementation of the Python dynamic programming language on Microsoft’s .NET framework and version 1.0 was formally released yesterday:
IronPython 1.0 Ships!!
IronPython is a project that implements the dynamic object-oriented Python language on top of the CLI. IronPython is both well integrated with the .NET Framework and is a true implementation of the Python language. .NET integration means that this rich programming framework is available to Python developers and that they can interoperate with other .NET languages and tools. All of Python’s dynamic features (such as, an interactive interpreter and the ability to dynamically modify objects) are available.
Microsoft’s Jim Hugunin recounts the history of its development at his blog and you can download IronPython 1.0 here.
Paul Krill at InfoWorld:
Microsoft has re-branded its WinFX technologies as .Net Framework 3.0 to clarify the naming convention for its developer framework, company representatives said on Friday.
.Net Framework 3.0 is planned for inclusion in Windows Vista, due out in early 2007. The framework features the Windows Communication Foundation Web services platform; the Windows Presentation Foundation presentation layer technology; Windows Workflow, for workflow; and the newly renamed Windows CardSpace, for identity management. CardSpace had been code-named InfoCard. Current .Net Framework 2.0 technologies, such as the CLR (Common Language Runtime), also are part of .Net Framework 3.0
“The .Net Framework has always been at the core of WinFX, but the WinFX brand didn’t convey this,” said S. “Soma” Somasegar, corporate vice president of Microsoft’s Developer Division, in his blog.
The Somasegar post is here and makes it clear that it is a name change only for all the .NET Framework 2.0 pieces. There are more details by following both the links, but there’s nothing that gets techies crankier than nomenclature so I expect there will be some complaints, particularly as this is a just a mash-up under a new name of technologies that previously had a separate life of their own. In any case, as expected (per Somasegar):
The .NET Framework 3.0 will still ship with Windows Vista, and will be available down-level for Windows XP and Windows Server 2003 as planned. This change doesn’t affect in any way the ship schedules of either Windows Vista or the .NET Framework 3.0 itself.
Update 6/21: Roy Osherove provides more information and a table that’s very helpful in puzzling out the .NET Framework versioning and future plans.