Template talk:Microsoft APIs

message: MDAC is not an API, it is a framework consisting of many components. As such, can we please change this to "Microsoft APIs and Frameworks"? - Ta bu shi da yu 01:40, 3 May 2007 (UTC)
thread_title:  MDAC is not an API 

message: Initially I was thinking removing both XHR and XDR, because the API was not developed by Microsoft, it was based on W3C's HTML 5 DOM. I am not sure if XDR is based on the W3C's HTML 5 that being said I guess that only leaves ToStaticHTML is developed by Microsoft, whether or not will it be included in ECMAScript Harmony we will just have to wait and see.
--Ramu50 (talk) 21:28, 7 November 2008 (UTC)
replies: text: XHR was originally developed by Microsoft (began it's life as an ActiveX component, and still has to be used that way for Internet Explorer 6.0 users), before it was standardized. I don't know whether or not it deserves a mention outside of MSXML, since it's part of the MSXML library (and I don't see any specialnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn mention for the ServerXMLHTTP component). The XDomainRequest is covered on Microsoft's IE Blog , and there is no standard that currently it applies to (see "Standards Information") . I have a feeling if you remove XHR, someone else will quickly add it back who hasn't read the talk page and it will be an ongoing battle to remove it. - Anphanax (talk) 03:08, 20 November 2008 (UTC)
thread_title:  Ajax API 

message: For starters Jeh, on one stated this template should be Driver "Developement". There is already a Template:Microsoft development tools and it is not necessary to let that particular section be limited.
In case you didn't know Jeh, ASIO is used by Creative Labs and suppported Microsoft for driver developement. Regardless it is specified by Steinberg and not Microsoft.
* Microsft JET Native ISAM Driver is an API layer that assist the ODBC so it can be can consider as drivers. Unlike most languages that are processed by parsers, API...etc. e.g. DOM API (AJAX) 
http://msdn.microsoft.com/en-us/library/ms714534(VS.85).aspx
 Used the SIMBA query processor produced by PageAhead Software. SIMBA received ODBC calls and 
 SQL statements, processed them into Microsoft Jet installable ISAM calls, and then called the 
 Microsoft Jet ISAM dispatch layer to load and call the appropriate installable ISAM driver.
http://msdn.microsoft.com/en-us/library/ms713553(VS.85).aspx
* The diagrams shows ISAM is a driver.
Also says by who you are allowed to have historical article in the template. That is purely biased. If you don't like Legacy products why not go ahead and delete the Windo Live Discontinued Products. --Ramu50 (talk) 21:00, 10 November 2008 (UTC)
replies: text: Just because they use the word "driver" doesn't mean it belongs in the same category with WDM, NDIS, etc. Jet is already in the template in the data access section, where it belongs. Putting it in the driver section is a case of "one of these things is not at all like the others." I have changed the section title to make the category more clear. Jeh (talk) 08:12, 11 November 2008 (UTC)

text: As for VxD, there's obsolete and then there's positively ancient. I seriously doubt that the typical template user needs a hook to VxD's here - if they already know about VxD's they can go straight to the relevant article; if they don't know about VxD's there is little need to learn about them at this point. It would be like having a link to "phlogiston" in a template regarding chemistry. But I will defer to editor Warren's opinion on the inclusion of VxD here. Jeh (talk) 08:12, 11 November 2008 (UTC)

text: Re ASIO, it's not a "Microsoft API". If it were, it would be in the Microsoft-published documentation, such as that for the Windows Driver Development Kit. It isn't. Jeh (talk) 08:40, 11 November 2008 (UTC)

text: p.s. "Jet" isn't mentioned in the WDK doc either. Jeh (talk) 07:24, 12 November 2008 (UTC)
thread_title:  Regarding Drivers 

message: There is no mention of this API currently, and yet there IS a mention of DDE (which is primarily used by the clipboard and not much else). OLE serves a different purpose, and although OLE 2.0 and later are built with COM, we're also listing other things that use COM (and OLE is NOT COM). It's also technically different than ActiveX as well. It's certianly not dead, given that microsoft continues to develop components that support OLE (e.g. Office, Windows Accessories Like Wordpad and Paint). - Anphanax (talk) 03:18, 20 November 2008 (UTC)
thread_title:  Object Linking and Embedding (OLE) 

message: Is there a way to come to some sort of agreement as to what is and is not included? We have a mention of VxDs, yet no mention of WinG, Media Control Interface (MCI), DirectDraw, or Collaboration Data Objects (CDO via CDOSYS or CDONTS). - Anphanax (talk) 03:25, 20 November 2008 (UTC)
replies: text: One way is WP:BRD. Another is to open a discussion here and see what consensus develops. Not too many people watch this talk page, so responses may be scarce. You might also check the edit history - in general if something that "obviously" belongs isn't here, it's because either the article in question doesn't exist yet, or nobody thought to put it in this template yet... unless it's in the edit history as having been deleted.  As I mentioned above I personally don't believe VxD needs to be in this list. Jeh (talk) 04:35, 20 November 2008 (UTC)
thread_title:  Obsolete and Deprecated APIs 

message: I see this template was last edited in 2016. Should UWP (Universal Windows Platform) be added for example? John a s (talk) 13:36, 20 August 2019 (UTC)
thread_title:  Updates for 2019 eg UWP