I am currently working on USD 1.0 which is of-course a very old version of USD.
We are trying to move to the newest version of USD in my organization, which i believe is USD 4.0
I have tried searching the web but other than the MSDN article i have been able to gather much detail on this version.
I am trying to figure out my possibilities in trying to adapt to this newer version. In light of it, i have a few questions listed below,
Has Microsoft released only the preview/trial version of USD 4.0 yet? Or is it made available for general public which means we can access and start developing in our production environment?
Is the new version of USD, a web based version? I have heard that
this version is not the desktop application like it was before.
Will it be safe to migrate from USD 1.0 to USD 4.0?
Microsoft has also introduced Unified Client Interface, what is it?
Is it available only with USD 4.0?
Features comparison with USD 1.0?
If Microsoft have released the preview version only, then when will
they release the stable version? (any tentative date)?
Also, if they have released the preview version just then obviously they might change it in future. Therefore, it will not be wise enough to migrate to it if it is just a preview version.
Looking forward to your answers. Any sort of videos, articles, documentations, press releases, your personal opinions are welcome.
Thanks
Most 'manual' based MSDN information has been moved to Microsoft Docs: https://learn.microsoft.com
USD 4.x is still a desktop application that loads MSD components. You can upgrade to a more recent version 3.2 quite easily:
You can upgrade a Unified Service Desk 1.x or Unified Service Desk 2.0 sample application package to Unified Service Desk 3.2 by importing the Upgrade sample application package. The upgrade will not affect the configuration data associated with the existing solution.
Follow the steps here:
https://learn.microsoft.com/en-us/dynamics365/customer-engagement/unified-service-desk/admin/upgrade-unified-service-desk-solution?view=dynamics-usd-3
From there on forward it is much more easy to compare 3.x with 4.x and answer all your remaining questions.
Neil Parkhurst also has a ton of information.
https://neilparkhurst.com/2016/06/20/usd-the-book/
Related
I am trying to find the FHIR 5.0 specifications and saw that some people seem to be using the FHIR v5.0 server already. According to the official FHIR blog, the specification was supposed to be released in the 3rd quarter of this year (of course COVID could have slowed this down). Could someone point me in the right direction please?
5.0 is in development and is scheduled to start balloting in May 2021. It's not likely to publish as a final 'official' release until Q2 2022. However, there's a "continuous integration build" that shows what the current proposed content for R5 is hosted here: http://build.fhir.org. As well, we produce snapshots of the draft R5 release for connectathons and other purposes so that there's a semi-stable release people can write code against when testing for connectathon.
The current timeline has indeed been impacted by COVID, but it's also been impacted by the appetite of the community for a new release and the ever increasing amount of work involved in producing a new release.
It is important to me to know whcih version of software should I use?
Last or Stable?
For example:
Laravel 5.5 (Stable) or Laravel 5.6 (Last)
cPanel 68.0.19 (Stable) or cPanel 68.1.1 (Last)
There are two options with Laravel:
Long Term Support
For those not familiar with long-term support, these are special versions that are feature locked at the date of release. They do not get any new features but keep getting bug fixes and security updates throughout the maintenance window.
For LTS releases, such as Laravel 5.5, bug fixes are provided for 2 years and security fixes are provided for 3 years. These releases provide the longest window of support and maintenance. For general releases, bug fixes are provided for 6 months and security fixes are provided for 1 year.
Version 5.1 was Laravel’s first LTS release.
LTS versions are popular with companies looking to reduce the risk, expense, and disruption of software deployment, while promoting the dependability of the software. It does not imply technical support.
Framework Releases
Major framework releases are released every six months (February and August), while minor releases may be released as often as every week. Minor releases should never contain breaking changes.
Using the latest release of the framework provides access to not only the latest security updates, but also new features. Updating your application to the latest release of the framework allows you to take advantage of new features and keeping migrations between subsequent versions relatively straightforward. It’s also an opportunity to refactor code to utilise the functionality of the framework. The work associated with upgrading is incremental, rather than the big jump between LTS versions.
If you follow the installation instructions (https://laravel.com/docs/5.5), you will be downloading the latest release of the framework.
We will be developing a new web site for a client who already has a Kentico 8.2 license. I am trying to make a case for developing the site using Kentico 9. Some key features I have found so far include:
faster performance (how much in real-world terms?)
better integration with .Net MVC
content staging tasks can be synchronized per user account
better rollback functionality: previously we had to make full database backups, content staging in Kentico 8.2 causes issues for restoring previous versions of a page.
built in source control support for GIT
It looks like Kentico integration with the client's existing database may be possible. Has anyone done this? What are the limitations or caveats?
Is there a discount for upgrading the license from 8.2 to 9?
Thanks in advance for your feedback!
faster performance (how much in real-world terms?)
there are major (official) improvements for content and contact management
better integration with .Net MVC
there is whole new way to develop sites using ASP.NET MVC with Kentico
content staging tasks can be synchronized per user account
there is pretty good blogpost describing new staging improvements
better rollback functionality: previously we had to make full database
backups, content staging in Kentico 8.2 causes issues for restoring
previous versions of a page.
I am not sure what do you mean by new rollback functionality
built in source control support for GIT
you might confused with continuous integration feature
You can find release notes with all new features and improvements here.
It looks like Kentico integration with the client's existing database
may be possible. Has anyone done this? What are the limitations or
caveats?
there is tested upgrade utility for upgrading to Kentico 9
Is there a discount for upgrading the license from 8.2 to 9?
for pricing you should definitely contact Kentico sales department
See the answer I posted on the DevNet (which by the way, no need to cross-post on both)
If they have a license for 8.2, is their maintenance current? If so, simply go to the client portal and upgrade it for free. This can be done without any cost. Either way, the licensing cost doesn't come from the version, it comes from the type (base, ultimate, ems, etc.).
So assuming they purchased their license about a year ago, their maintenance should be current or close to current and you either get current on your maintenance or just go to the client portal and see if it will allow you to upgrade your license and get a new key for v9.
If they don't have the site built, there is no reason to build it on v8.2 at all.
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.
As the question states, I am preparing to deploy my first couple modules on the Magento Connect store and want to make sure I am targeting the best versions. Testing on 1.3 is proving to be a bit of a pain, and if only a few people use that version I would rather spend the time making the modules better!
Google hasn't helped as yet, though I think the keywords I use are getting picked up as other more specific technical questions (Google Base, for example).
Does this information exist? What about your personal experience? For me, I have only encountered installations below 1.5 Community (1.10 Enterprise) for upgrade projects. I haven't personally encountered a client that is on 1.4 and plans to stay on 1.4.
Thanks!
Tim
There are a signification amount of people who have older versions and wont upgrade because of the complexity and the amount of modification they have done to their stores.
Most people right now who are on community version seem to be on 1.5 or 1.6, but if you want to test older versions just download from the archive install locally and see if it works for the older versions.
Here is a link to the downloadable versions of magento, in case you decide to test on those older versions:
http://www.magentocommerce.com/download - click released archived tab at the top