MSDN auto redirection always opens the ANSI API function page
-
Triggered by Richard's post below. What annoys me really is that they did not get the redirection of MSDN pages to MS Docs work properly. If you have a MSDN link for a wide version of an API function, it redirects to the ANSI version at MS Docs! That happens even when already at Docs because all the links are MSDN links. Open for example GetFileVersionInfoExW function | Microsoft Docs[^] and follow links there like the one shown as
GetFileVersionInfoSizeExwhich links to https://msdn.microsoft.com/library/Aa969435(v=VS.85).aspx. But that is automatically redirected to Docs which is then GetFileVersionInfoSizeExA function | Microsoft Docs[^] instead of the expected GetFileVersionInfoSizeExW function | Microsoft Docs[^]. As a result, all existing answers here at CP and elsewhere containing MSDN links to API functions will now open the ANSI version when clicked. Another side effect is when inserting MSDN links now here at CP, the ANSI title from the Docs page is inserted while the link itself is still to MSDN. -
Triggered by Richard's post below. What annoys me really is that they did not get the redirection of MSDN pages to MS Docs work properly. If you have a MSDN link for a wide version of an API function, it redirects to the ANSI version at MS Docs! That happens even when already at Docs because all the links are MSDN links. Open for example GetFileVersionInfoExW function | Microsoft Docs[^] and follow links there like the one shown as
GetFileVersionInfoSizeExwhich links to https://msdn.microsoft.com/library/Aa969435(v=VS.85).aspx. But that is automatically redirected to Docs which is then GetFileVersionInfoSizeExA function | Microsoft Docs[^] instead of the expected GetFileVersionInfoSizeExW function | Microsoft Docs[^]. As a result, all existing answers here at CP and elsewhere containing MSDN links to API functions will now open the ANSI version when clicked. Another side effect is when inserting MSDN links now here at CP, the ANSI title from the Docs page is inserted while the link itself is still to MSDN. -
I never liked the newer version of the documentation. Probably because I'm an old fart who likes to see documentation that is actually designed for programmers to read.
Same for me. But the MSDN online documentation is gone now. The only advantage is that the links are now meaningful.
-
Same for me. But the MSDN online documentation is gone now. The only advantage is that the links are now meaningful.
-
Triggered by Richard's post below. What annoys me really is that they did not get the redirection of MSDN pages to MS Docs work properly. If you have a MSDN link for a wide version of an API function, it redirects to the ANSI version at MS Docs! That happens even when already at Docs because all the links are MSDN links. Open for example GetFileVersionInfoExW function | Microsoft Docs[^] and follow links there like the one shown as
GetFileVersionInfoSizeExwhich links to https://msdn.microsoft.com/library/Aa969435(v=VS.85).aspx. But that is automatically redirected to Docs which is then GetFileVersionInfoSizeExA function | Microsoft Docs[^] instead of the expected GetFileVersionInfoSizeExW function | Microsoft Docs[^]. As a result, all existing answers here at CP and elsewhere containing MSDN links to API functions will now open the ANSI version when clicked. Another side effect is when inserting MSDN links now here at CP, the ANSI title from the Docs page is inserted while the link itself is still to MSDN.Quote:
06/11/2018
Well, if you will insist on reading documentation three months before it's published... :laugh:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Jochen Arndt wrote:
The only advantage is that the links are now meaningful.
:laugh: :laugh: :laugh:
Hey, you can fix the links - once opened - by replaciny the trailing 'A' with a 'W'. That wasn't possible (and necessary) with the MSDN numeric links.
-
Hey, you can fix the links - once opened - by replaciny the trailing 'A' with a 'W'. That wasn't possible (and necessary) with the MSDN numeric links.
