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.
Related
I installed Latest Version of Developer Toolkit for vs2015 and after that when i use toolkit to connect to CRM, after click on connect button it does not do anything. no error, no success action,
i delete every Cache data and every Temp data and Clear my solution but nothing change,
do you have any idea? help me please because i want to develop custom workflow step and develop plugins with this toolkit.
As far as I know, Microsoft's Developer's Toolkit has been dormant for quite some time.
Current options are:
Jason Lattimer's Developer Extensions
Which is also on GitHub.
Or the commercial add-on XrmToolkit, which has a 30-day free trial.
If you go with Jason's solution and you're looking to do early bound development you might want to also look into XrmToolbox's Early Bound Generator by Daryl LaBar.
The XrmToolkit includes its own proprietary proxy class generator.
I have developed bot application using Microsoft bot framework V4 preview(4.0.1 Preview)
Now i want to migrate to new stable version (4.0.8)
Can anyone tell me what are the breaking changes and how to fix those..
The downvotes are probably because this is a very broad question, as the framework went through some pretty significant changes from Preview to Stable. For example, if I'm not mistaken, what you call DialogContainer is probably ComponentDialog now. No one's going to be able to say what the breaking changes are, because they broke in different places for different bots, depending on the the bot's code. If you attempt to upgrade to 4.0.8 and run into errors, you can post those errors and get better assistance in solving each one.
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.
I am pretty new in source control installation and inner workings, although I already had worked with TFS, I have no clue about how to make it work from scratch.
Basically I want to have some source control in my personal VS2010 projects, so I may see the code evolution, rollback and etc. but I am a little lost about how may I set it up...as far as I can see, I have to have a Team Foundation Server running, so is it possible to install one in my PC? Is it free? Or there is a better way for doing it?
I just want some simple tips like "hey man, here are the steps you should follow" or "this is impossible, you have to have a server" or "follow this tutorial"
Thanks a lot guys!
[Disclaimer: I work on TFS and tfspreview.com]
If you are looking for ease of set up and a free offering then I would highly recommend tfspreview.com. While it is still in "preview" mode, it is certainly usable and safe. The site itself also has a great "learn" section to help you get started. The best part is that it has features available that haven't even been released in the on-premises product yet and the development team is consistently adding new features.
If you have any questions about the service, I'd be glad to answer them.
Oh, one other note, to connect to the hosted service you will need to install the VS 2010 compatibility GDR but that is free also.
GIT is a brilliant source control that has allot of easy to use functionality. In fact that have an extension for VS2010 as well. Check under the extensions menu and install the GIT extension. You can them commit and update from within VS itself. Super easy to use!
Enjoy :)
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.