Windows 7 Application Compatibility Manifest Will Impact Windows 8

Last Updated on Monday, 20 July 2009 10:00 Written by Mire_B Monday, 30 March 2009 02:15

And all Windows releases for that matter.
Here is a sample offered by Chris Jackson, an Architect and the Technical Lead for the Windows Application Experience SWAT Team:
<?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes”?>
<assembly xmlns=”urn:schemas-microsoft-com:asm.v1″ manifestVersion=”1.0″>
<compatibility xmlns=”urn:schemas-microsoft-com:compatibility.v1″>
<application>
<!–Windows 7–>
<supportedOS Id=”{35138b9a-5d96-4fbd-8e2d-a2440225f93a}”/>
<!–Windows Vista–>
<supportedOS Id=”{e2011457-1546-43c5-a5fe-008deee3d3f0}”/>
</application>
</compatibility>
</assembly>
Jackson’s explanation:
“The argument for GUIDs (Globally Unique Identifier): Nobody knows what the GUID for Windows 8 is going to be yet. Not even us. So, by using GUIDs, we prevent somebody from claiming compatibility with an operating system they can’t possibly have tested with. (Odd that we’d be so against such a thing in one group, while the IE team gives you the X-UA-Compatible option of edge to do exactly that.)The argument against GUIDs: You’re punishing the good guys in order to prevent the bad guys from shooting themselves in the foot. If I test something on Windows 8, and add its GUID to my manifest, I’m going to get both the Windows 8 and Windows 7 fixes (since the OS will simply look at the highest version and apply all previous fixes). But, if I *only* put in the Windows 8 GUID, on Windows 7, I won’t recognize the Windows 8 GUID (since it doesn’t exist yet), and not only will I not give it the Windows 8 fixes, I won’t give it the Windows 7 fixes either. And, if the only fixes I actually needed were the Windows 7 ones, I just broke the app.”

Application Manifest (source MSDN)

[This documentation is preliminary and is subject to change.]

Affected Platforms

Clients – Windows 7
Servers – Windows Server 2008 R2

Feature Impact

Severity – Low
Frequency – Low

Description

Windows 7 introduces a new section in the application manifest called “Compatibility.” This section helps Windows determine the versions of Windows that an application was designed to target, and enables Windows to provide the behavior that the application expects based on the version of Windows that the application targeted.

The Compatibility section allows Windows to provide new behavior to new developer-created software while maintaining the compatibility for existing software. This section also helps Windows deliver greater compatibility in future versions of Windows as well. For example, an application declaring support only for Windows 7 in the Compatibility section will continue to receive Windows 7 behavior in future version of Windows.


Learn More

Windows 7 Service Pack 1 (SP1), a Long Way from Windows Vista SP1

Last Updated on Tuesday, 24 March 2009 12:27 Written by Mire_B Tuesday, 24 March 2009 12:22

Never too early to talk future Windows releases, if you ask me. But is it stretching it to start the discussion about Windows 7 Service Pack 1? Not actually. Because the focus is not the service pack itself, but whether Windows 7 will be sufficiently mature post-RTM in order to convince customers, and especially businesses, from SMBs to large corporations, to embrace the platform ahead of SP1.

 

According to Gartner: “The first Service Pack for Windows 7 is not necessary for the operating system’s stability and security readiness. However, organizations likely won’t be ready to deploy Windows 7 before SP1 ships, so they will include it in their initial deployments.”

 

What Gartner is trying to say is a simple “don’t wait for Windows 7 SP1″ in order to upgrade/migrate.  The conclusion reads as following: “Organizations should not expect to deploy Windows 7 until 12 to 18 months after the OS ships. Although SP1 will probably be part of the initial deployment image, organizations won’t be waiting for it because other requirements will take longer to resolve. Including SP1 with Windows 7 could result in increased stability because fewer changes need to be introduced to the environment over the life cycle. ”

 

I’ve been running Windows 7 since Milestone 3, and I was also one of the first adopters of Vista. Organizations don’t need to wait for Windows 7 SP1, says Gartner. But end users also will not need to wait for SP1 in order to embrace the operating system. If it will be good enough as RTM for companies with thousands of machines to deploy, it’s bound to be sufficiently “ready” for the public.

 

Vista indeed needed SP1 to make it usable, reliable, stable, etc., it needed the maturity of the hardware and software ecosystem which had to go through a paintful adaptation after the cozy Windows XP. The evolution from Windows 6.0 to Windows 6.1 will be at the opposite pole.

 

Below the rest of Gartner’s research:


Learn More

Internet Explorer 8 (IE8) – The Essential Microsoft Download Center

Last Updated on Sunday, 22 March 2009 08:58 Written by Mire_B Thursday, 19 March 2009 02:22

Call it released to web (RTW) or released to manufacturing (RTM), or even gold, but fact is that Internet Explorer 8 (IE8) is now available for download. Links:


Learn More
Designed by CodenameWindows
WordPress is Free Software released under the GNU/GPL License.