Bug 68203 - LibreOffice main executables should have a compatibility manifest
Summary: LibreOffice main executables should have a compatibility manifest
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
4.2.0.0.alpha0+ Master
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Installer-Windows
  Show dependency tree / graph
 
Reported: 2013-08-16 18:32 UTC by Jesus Corrius
Modified: 2019-04-12 09:54 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jesus Corrius 2013-08-16 18:32:04 UTC 
The compatibility section of the app manifest helps the operating system provide your app the proper compatibility behavior under different versions of Windows.

Review the following documentation carefully:

http://msdn.microsoft.com/en-us/library/hh848036(v=vs.85).aspx
Comment 1 V Stuart Foote 2013-08-18 18:13:29 UTC 
Jesús,

What is the impact that we don't?  And if we do, would setting LO as a Windows 7 app--including a manifest with target GUID {35138b9a-5d96-4fbd-8e2d-a2440225f93a} as in the Technote--in anyway impact its use on XP or Vista?

Does adding the compatibility manifest just provide a more complete "registration" of LO into Windows 7 and Windows 8?  What does the project gain moving the Windows implementation further into MS compliance?

Are there practical reasons?  Does adding the compatibility manifest have a functional impact and improve integration--perhaps of the Windows 7 Jumplist functions, for both Windows 7 and Windows 8 installs? 

Would it facilitate in some fashion features unique to Windows OSs--perhaps the Live Tiles on the Windows 8 Modern UI Start screen? Or might it be helpful should anyone undertake a branch of LO as a MS App?

Stuart
Comment 2 Jesus Corrius 2013-08-18 20:08:21 UTC 
Hi Stuart,

For now, I just want to add a default one with Windows Vista behaviour so it will have no impact on the application. I expect to ship 4.2 with this one unless there's one or more options that really make a difference for us.

There are some tweaks for Windows 8, and also 8.1, that I think are worth exploring (p.e DPI compatibility for embedded devices and special screens, etc). But let's see that later. Any change will require a lot of testing.

In this bug I just want to add the manifest. Microsoft recommends to use one in all new applications so at least we will be following the best practices. Of course, I hope we will be able to use it for more than that!

J.
Comment 3 QA Administrators 2015-04-01 14:41:27 UTC Comment hidden (obsolete)
Comment 4 tommy27 2016-04-16 07:27:41 UTC Comment hidden (obsolete)
Comment 5 Andras Timar 2016-04-16 08:06:09 UTC 
We still don't have the compatibility manifest.
Comment 6 QA Administrators 2017-05-22 13:24:52 UTC Comment hidden (obsolete)
Comment 7 V Stuart Foote 2017-05-22 14:30:10 UTC 
Still an issue...
Version: 5.3.3.2 (x64)
Build ID: 3d9a8b4b4e538a85e0782bd6c2d430bafe583448
CPU Threads: 8; OS Version: Windows 6.19; UI Render: GL; Layout Engine: new; 
Locale: en-US (en_US); Calc: group

@Jesus, you still with us?
Comment 8 QA Administrators 2018-05-23 02:37:52 UTC Comment hidden (obsolete)