E.g. I search “JetCommitTransaction”, search finds https://msdn.microsoft.com/en-us/library/gg269191(v=exchg.10).aspx which redirects to https://learn.microsoft.com/en-us/previous-versions/
That API is available in all versions of Windows starting from Win2000 to the very latest Win10, and even available for Windows 10 UWP apps, https://learn.microsoft.com/en-us/uwp/win32-and-com/win32-apis#apis-from-esentdll so it’s not deprecated or something.
archive.org works but it's slow and inconvenient.
Microsoft is moving all documentation from msdn.microsoft.com to learn.microsoft.com so I assume this will work itself out after a while but this is the first time I have seen a completely broken redirect.
I think Google cache and Archive.org are your best options for now. You could also try contacting #docsmsft/Github issues.
We are working on moving all MSDN documentation to learn.microsoft.com. Some of the redirects were accidentally deployed early - those have been rolled back, until the migration is complete. In the meantime, the documentation is accessible on MSDN on the links you specified above.
Related
I am using sdk v4 bot embedded in sharepoint 2016 page using iframe webchat https://webchat.botframework.com/embed/[Token] url. It stopped working in IE 10. I remember it worked before 3 weeks. Please help as we put the bot in production.
There was a recent update to webchat, so I'm guessing this is a webchat version issue. Do you have the ability to use directline channel with botframework-webchat instead? There are a number of samples. In the getting-started full-bundle sample, you can see where the latest version is specified. You can use this to specify a later version, though I'm not sure if it will let you go far enough back.
You are also going to need to customize the formatting, as the new webchat comes through with essentially no formatting. There are a number of samples on that site showing the different formatting options as well.
For shorter term fix, you may be able to request your specific bot app ID to be reverted by contacting the Microsoft contact from this github issue, though I would recommend also working on updating your implementation as that probably won't be available forever.
This was pompted by a couple of recent questions where the answer amounted to "there seems to be no API for that" in both cases.
Retrieving Windows version "1511" was about retrieving the "Version 1511" string prominently displayed in the Help / About boxes of system apps from Notepad to MMC since the November update. The only proposed workaround was to read it off an undocumented registry key.
How to detect whether Windows 10 features are currently enabled in the console was about a console app detecting whether it's running under the "new" console (ForceV2=1) vs. the legacy console. An incomplete and unsatisfactory workaround (that I posted there) was to check whether the console window allows itself to be resized wider.
I would expect that there must be more cases of such new features that the published APIs haven't caught up with, yet. Examples welcome, references and known workarounds even better.
The inability to obtain a version number is entirely intentional. Both GetVersion(Ex) and VerifyVersionInfo are deprecated, although they are still available for Windows desktop apps. The use of GetVersion(Ex) is strongly discourage, and VerifyVersionInfo should really only be used for you must be this high to ride this ride checks. See this post and this one.
Universal Windows apps have access to an opaque string for logs and telemetry, but apps shouldn't be trying to display a user-visible version number. See AnalyticsInfo.VersionInfo. In short, if you are UWP you already know you are on Windows 10. If you have hard dependencies on a particular version, that is handled through AppX manifest elements.
I have seen that yesterday Web API RTM has been released by Microsoft.
However I can't seem to find any log about what has changed from RC to RTM and any tips on what has changed.
We have a service that's ready for production next week, and I am not sure whether to roll with RC or upgrade to RTM this late in the project. What value does it add?
Thanks
Ubal
The official release notes can be found here at www.asp.net.
As #Aliostad kindly mentioned, I wrote an overview post highlighting what's changing and including some code samples and other references.
Henrik also wrote a nice overview post - and that one's also focused on the preview for the out-of-band functionalities available as NuGet packages (OData, tracing, Help page, and a formatting library for Win8).
If you ask whether you should upgrade - obviously yes. There aren't many breaking changes so it should be rather painless, and you get a mature, production-deployable product. It's well worth it imho.
Since Google stopped supporting Notebooks, I decided to look for alternatives and so I gave TiddlyWiki + TiddlySnip a shot. However, when trying to install TiddlySnip2.1, I'm getting this error:
"TiddlySnip" will not be installed because it does not provide secure updates
I followed the procedure specified in the site which is to add tiddlysnip.com in the Allowed sites-Add ons list but it still won't work.
And to add insult to injury, the support for the extension has been stopped as well.
My final workaround is to use an older version(1.21-beta), which I was able to find, but I'm finding it a bit unstable.
Did anyone have any success with this?
Thank you.
Eureka! Google has saved me! Their google group has a post on how to shoehorn it into Firefox 3.5.x: http://groups.google.com/group/tiddlysnip/browse_thread/thread/e5edef97dec18a17/ce49452f6397083a?lnk=gst&q=does+not+provide+secure+updates#ce49452f6397083a
Right Stumproot, however I just feel the need to look for alternatives.
OT, I went as far as going into the irc channel of tiddlywiki to find out and it seems that there's no other way around this issue than to use the older version.
I think that the TW community still plans to continue developing TiddlySnip but for now it's on hold so TW users will just have to make do with the beta version.
How do I let Microsoft know about a problem I've found in one of their core library routines? Do they have a central repository to report these things?
I am not a member of Microsoft Development Network (MSDN).
Or should I even bother?
There is no official way to report bugs to Microsoft for an end-user. If you are participating in a beta program for an upcoming release, the beta program includes a bug-reporting channel. Otherwise, if the bug causes problems that you want to get resolved, you can call Microsoft support, and they will help you solving the problem (be it by providing a patch, or a work-around); if the problem turns out to be caused by a bug indeed, they will refund the costs of the support call.
Microsoft does have a central repository (perhaps separate ones per product), but this repository is not accessible for the general public.
If it's a documentation bug (or if the documentation should call it out), you can get good results with the Feedback links in MSDN library. You can report bugs in Microsoft developer tools (among other things) by signing up at connect.microsoft.com.
If you're sure you've found a bug in a core library routine, you can raise a PSS (support case. It'll cost you money, but if it turns out you're right (and they issue you a hotfix), I think that they refund the money.
I've never been so confident that I've found a bug that I'm willing to make that gamble.
I don't know why ChrisN took back his answer. I saw it earlier today when he had it up, He said:
You can report bugs on the Microsoft Connect website (I've done this in the
past). You don't have to have an MSDN
subscription.
I had not heard of the Microsoft Connect website, but when I used the search box there to search for "Registry Unicode", the first entry listed was a bug very similar to the one I encountered. And clicking through on that entry led me to look at the conversation that appears to be Microsoft people addressing the issue, passing it on to appropriate people and escalating it as necessary.
I have no experience with the Microsoft Connect website, but if it turns out to be as promising as it appears, this may be the answer to my question.