Monday, September 22, 2003
.NET Compact Framework and Product Cycles
Posted by Andy Sjostrom in "DEVELOPER" @ 02:00 AM
Microsoft introduced .NET Compact Framework in ROM as of Pocket PC 2003 and Smartphone 2003. This means that developers can use Microsoft's new tools and languages to develop software not only for desktop and server solutions, but also for mobile solutions. The primary advantage of putting the .NET Compact Framework in ROM is that developers don't have to redistribute the components, between 2 and 3 MB, every time a new application is to be shipped. This advantage went away to some extent when Microsoft released a Service Pack for the .NET Compact Framework weeks after the release of Pocket PC 2003, the so called .NET Compact Framework 1.0 SP1 Redistributable. The Service Pack contained a number of defect fixes some of which lead to performance improvements.
Don't get me wrong. I love defect fixes and performance improvements. The fact that Microsoft just release yet one more Service Pack the .NET Compact Framework 1.0 SP2 Developer Redistributable is proof of that the team is committed to deliver the best bits as soon as possible. Since the changes don't break any developers existing code everyone should be pleased. But I think one piece of the puzzle is missing: the advantage of having .NET Compact Framework in ROM is broken if every developer needs to revert back to the old habit of redistributing 2-3 MB runtime files for each new application.
I have learned that the .NET Compact Framework team's product cycle is tied to that of Visual Studio .NET and not to that of mobile devices. This means that we will see product and service pack releases sometimes in sync and sometimes out of sync. However, I would love to see two things:
1. More frequent End User Updates updating the ROM of Pocket PCs and Smarphones with the latest .NET Compact Framework bits.
2. A slip stream release of the latest .NET Compact Framework builds into the device makers production lines.
I have asked Microsoft to respond to these questions and will report back when they do!
Don't get me wrong. I love defect fixes and performance improvements. The fact that Microsoft just release yet one more Service Pack the .NET Compact Framework 1.0 SP2 Developer Redistributable is proof of that the team is committed to deliver the best bits as soon as possible. Since the changes don't break any developers existing code everyone should be pleased. But I think one piece of the puzzle is missing: the advantage of having .NET Compact Framework in ROM is broken if every developer needs to revert back to the old habit of redistributing 2-3 MB runtime files for each new application.
I have learned that the .NET Compact Framework team's product cycle is tied to that of Visual Studio .NET and not to that of mobile devices. This means that we will see product and service pack releases sometimes in sync and sometimes out of sync. However, I would love to see two things:
1. More frequent End User Updates updating the ROM of Pocket PCs and Smarphones with the latest .NET Compact Framework bits.
2. A slip stream release of the latest .NET Compact Framework builds into the device makers production lines.
I have asked Microsoft to respond to these questions and will report back when they do!
