📜 ⬆️ ⬇️

Windows Home Server SDK published

Once I started with a trivial, but long post. To correct, short and more meaningful from the same place.

Today we published the MSDN Windows Home Server SDK. Our General Manager Charlie Kindell just announced this on our main English blog under the heading <a href = "/ homeserver / archive / 2007/04/03 / developers-developers-developers.aspx" mce_href = "/ homeserver / archive / 2007 /04/03/developers-developers-developers.aspx"> ourDevelopers, Developers, Developers. The SDK itself can be found here: <a href = " msdn2.microsoft.com/en-us/library/aa306570.aspx " target = "_ blank" mce_href = " msdn2.microsoft.com/en-us/library/aa306570. aspx "> http://msdn2.microsoft.com/en-us/library/aa306570.aspx

Just to quote the key point of this post (in my free translation):
')
But in reality, 99% of what developers want to build on top of Windows Home Server will be done using the rest of the MSDN documentation. Our small set of program interfaces will allow you to integrate your add-ins into the WHS console and interact with some parts behind the solutions we provide. But all the interesting work that these <a href= msdn2.microsoft.com/en-us/library/aa306570.aspx "will do" mce_href= a msdn2.microsoft.com/en-us/library/aa306570.aspx ”> add-ons will be made using the standard “Windows API” (meaning Win32, COM, COM +, .Net 2.0, and everything else available on any other Windows)




It should be noted that the ability to "insert" in the WHS console is an important thing. The main configuration of WHS will be without a monitor and keyboard, the console is essentially the only way to communicate with the user. Plus, there will be opportunities to work with backups, volumes, folders, users, as well as the ability to create notifications, which come out on client computers from a reddened or yellowed tray icon at the bottom right. How about a “red alert” “Stop having fun, dinner is getting cold!”

Source: https://habr.com/ru/post/6903/


All Articles