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.
Related
I've recently started to get into Camunda (version 7). I have already develoiped a few workflows, and everything is running smoothly, including the basic Cockpit, which I find highly useful.
Now I want to put my workflows into production. What are the limitations of doing so, using only the Community edition, instead of the Enterprise one? Am I losing out on something important by not going for the full commercial service?
Will I encounter any limitations down the road that will block my workflows?
You can find a comparison of Camunda 7 CE and EE here:
https://camunda.com/enterprise/
There is no (e.g. volume) limitation on engine level you will be surprised by later on. Apart from commercial support, the additional Cockpit features are very useful and Optimize to add business analytics to your environment may also be of interest.
So far they're the only people I can find that are doing a chart control...
What happens when the beta expires? How does it expire? (Does it expire?). They look great but there is no pricing information or expiry information.
Here is a direct quote from the EULA:
“You may distribute the Programs as embedded in Your Integrated Products to Your end-users only pursuant to an end-user license that meets the requirements of this Section.”
So, yes, you can ship Apps built with Telerik Windows 8 Controls Beta to the Store.
"Beta," by definition, suggests not ready for production use.
There are at least a couple of things you should think about before moving forward:
Does the license agreement for the controls allow use in a production app (you did read the license, right?)
Are you willing to risk the possibility that the app might suddenly stop working for any and all users who have downloaded it, until such time as you replace the controls with working versions (and get the updated version of your app submitted to the store)?
As long as the controls fit the Windows 8 app design, and don't cause performance or crashing issues, they may not have any impact on whether or not the app gets through certification.
But the larger issue is one of risk. Betas are for testing. IMO, unless the beta includes a "go-live" license, you should probably stick with using beta software for evaluation and testing only.
To be clear, that's no knock on Telerik's beta quality (or anyone else's, for that matter). Just a reminder that beta software isn't finished yet.
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
Hi
we are upgrading websphere application server(WAS) from v6.x to 7.x
currently WAS is installed at:
/usr/IBM/WebSphere/AppServer - default location.
What is the best way to upgrade to 7.x, and recreate profiles with least downtime?
If you are talking just about WAS with no extra IBM products (like Portal, Quickr, Connections, etc) on top of it your best off setting up a new fresh one next to your old one and manually making the configurations (data sources etc). It takes only couple hours to install and update one and if your applications have decent documentation about their requirements it shouldn't take more than a few hours to set up the rest... Then you can simply test it and redirect the traffic.
I am mainly interested in the 'integration features' between the IDE and the application server.
One example would be GUI editors for various server specific deployment descriptors.
Another example, from the NetBeans IDE integration with GlassFish, is the ability to:
edit a java file that is part of a
web application,
save the file and
see the effect of the change that you
just saved in the browser (without a
bunch of reloading).
Please include a link to any reference to the feature in user docs, if you have it at the tips of your fingers.
Over my years using RAD, the feature I'd recommend everybody to use would be its uninstaller...
Seriously though, RAD's advantage used to be IBM's plugins for Web / J2EE development; over the years, though, the Eclipse community has been making great progress with WTP and JST, so for most J2EE development you should do fine using Eclipse+WTP+JST... which are free (comparing RAD with 5-10K USD licensing fees. Per machine, that is).
One person suggested that the 'Web site navigation' tooling was useful.