Is there a UX guidelines regarding naming application shortcuts in Windows ?
-
( I hope my description is clear enough) We allow installing major versions of our application in parallel (for example, 1.0, 2.0, 3.0) For minor versions releases, we patch the current version (for example 1.1, 2.4, 3.2 ... ) and we rename the shortcuts (start menu and desktop) to reflect the minor version (for example, app 1.1, app 2.4 ) Question: Is there a Microsoft UX guideline saying what behavior Windows application should do in that case ? For example, the Visual Studio shortcut will only display the major version , but not the update number , for example "Visual Studio 2015" and not "Visual Studio 2015 Update 3" Thanks.
I'd rather be phishing!
-
( I hope my description is clear enough) We allow installing major versions of our application in parallel (for example, 1.0, 2.0, 3.0) For minor versions releases, we patch the current version (for example 1.1, 2.4, 3.2 ... ) and we rename the shortcuts (start menu and desktop) to reflect the minor version (for example, app 1.1, app 2.4 ) Question: Is there a Microsoft UX guideline saying what behavior Windows application should do in that case ? For example, the Visual Studio shortcut will only display the major version , but not the update number , for example "Visual Studio 2015" and not "Visual Studio 2015 Update 3" Thanks.
I'd rather be phishing!
I've never come across a standard convention for this (and I've been around the block a few times :laugh:). Couldn't find one either. I have seen the convention you have noted "Visual Studio 2015" etc from other major suppliers. By the same token NUnit includes the minor e.g. 2.6.3 as does Windows Phone SDK e.g. 8.1 I'm personally not a fan of changing the shortcut just because there has been an update but I guess you have no choice if you are allowing parallel installs. However that leads me to yet another style (I won't call it a convention any more) that is common and that is to have the Start Menu folder name static with the (major) versions listed below. Probably not a lot of help, but no-one else responded
-
( I hope my description is clear enough) We allow installing major versions of our application in parallel (for example, 1.0, 2.0, 3.0) For minor versions releases, we patch the current version (for example 1.1, 2.4, 3.2 ... ) and we rename the shortcuts (start menu and desktop) to reflect the minor version (for example, app 1.1, app 2.4 ) Question: Is there a Microsoft UX guideline saying what behavior Windows application should do in that case ? For example, the Visual Studio shortcut will only display the major version , but not the update number , for example "Visual Studio 2015" and not "Visual Studio 2015 Update 3" Thanks.
I'd rather be phishing!
-
I've never come across a standard convention for this (and I've been around the block a few times :laugh:). Couldn't find one either. I have seen the convention you have noted "Visual Studio 2015" etc from other major suppliers. By the same token NUnit includes the minor e.g. 2.6.3 as does Windows Phone SDK e.g. 8.1 I'm personally not a fan of changing the shortcut just because there has been an update but I guess you have no choice if you are allowing parallel installs. However that leads me to yet another style (I won't call it a convention any more) that is common and that is to have the Start Menu folder name static with the (major) versions listed below. Probably not a lot of help, but no-one else responded
Good question and Happy Independence day 2018 Whatsapp status[^]
-
( I hope my description is clear enough) We allow installing major versions of our application in parallel (for example, 1.0, 2.0, 3.0) For minor versions releases, we patch the current version (for example 1.1, 2.4, 3.2 ... ) and we rename the shortcuts (start menu and desktop) to reflect the minor version (for example, app 1.1, app 2.4 ) Question: Is there a Microsoft UX guideline saying what behavior Windows application should do in that case ? For example, the Visual Studio shortcut will only display the major version , but not the update number , for example "Visual Studio 2015" and not "Visual Studio 2015 Update 3" Thanks.
I'd rather be phishing!
Great info.
-
( I hope my description is clear enough) We allow installing major versions of our application in parallel (for example, 1.0, 2.0, 3.0) For minor versions releases, we patch the current version (for example 1.1, 2.4, 3.2 ... ) and we rename the shortcuts (start menu and desktop) to reflect the minor version (for example, app 1.1, app 2.4 ) Question: Is there a Microsoft UX guideline saying what behavior Windows application should do in that case ? For example, the Visual Studio shortcut will only display the major version , but not the update number , for example "Visual Studio 2015" and not "Visual Studio 2015 Update 3" Thanks.
I'd rather be phishing!
TechUpdatesDaily A resource where one can find the latest updates & news about technology, software, gadgets and business ideas for the start-ups.
WebUpdatesDaily -
I've never come across a standard convention for this (and I've been around the block a few times :laugh:). Couldn't find one either. I have seen the convention you have noted "Visual Studio 2015" etc from other major suppliers. By the same token NUnit includes the minor e.g. 2.6.3 as does Windows Phone SDK e.g. 8.1 I'm personally not a fan of changing the shortcut just because there has been an update but I guess you have no choice if you are allowing parallel installs. However that leads me to yet another style (I won't call it a convention any more) that is common and that is to have the Start Menu folder name static with the (major) versions listed below. Probably not a lot of help, but no-one else responded