Recently I have been reading the article by Microsoft What's new in .NET Core 3.0
and in its part
.NET Core SDK Windows Installer
The MSI installer for Windows has changed starting with .NET Core 3.0. The SDK installers will now upgrade SDK feature-band releases in place. Feature bands are defined
in the hundreds groups in the patch section of the version number. For
example, 3.0.101 and 3.0.201 are versions in two different feature bands while 3.0.101 and 3.0.199 are in the same feature band. And,
when .NET Core SDK 3.0.101 is installed, .NET Core SDK 3.0.100 will be
removed from the machine if it exists. When .NET Core SDK 3.0.200 is
installed on the same machine, .NET Core SDK 3.0.101 won't be removed.
I have found for the first time the term feature band. Could someone please explain what exactly this term means in this context?
It means when they change the third version number by the hundreds they also change the UpgradeCode to allow it to install side by side.
I have created a Module(Portal). I am going to publish it. I just don't know which version it can support. The previous versions and future versions. I am just curious above this all specially in case of .DLLs.
Please suggest me.
Development system
1- Visual Studio 2015
2- DotnetNuke 7
DLLs
It will all depend on what version of the DotNetNuke.DLLs you compile your module against.
Typically if you compile against a version, say 07.00.01, the module will run on that version AND any NEWER version of DNN.
There are some cases where there are breaking changes for modules on upgrade of the DNN version, but they are pretty few and far between.
Looking at the project.json file in this question and looking at other questions on SO about RC2 makes me think that RC2 has been released. But I cannot find any official announcement that it has been released. Does anyone know if it's been released? If so, can you install it on top of RC1 or are there special installation procedures?
APS.Net Core RC2 will in all likelihood be released on or before 5/17/16 as Damian Edwards mentioned at the ASP.Net Community Stand-up on 5/10/16. As to the link you referenced, they are using nightly builds. You can actually get bits now from the nightly stream that are labeled "Microsoft.AspNetCore.Mvc": "1.0.0-rc3-*" as the team has continued to finish polishing things up for release. These ports will end up being renamed to whatever management decides to call the final build. The Nuget server for Microsoft Nightly builds is https://www.myget.org/F/aspnetcidev/api/v2/ You can add it to Visual Studio by going to Tools=>Options=>NuGet Package Manager=>Package Sources.See NuGet Package Manager Image Here. However, being so close to a supported release version, it seems futile now. I assume Microsoft will support RC2 with a "Go-Live" license.
To be more specific.
ASP.Net Core RC2 will be released ither today (friday), or on tuseday next week.
From what I know, everything is done and set in escrow.
Only the tooling team is tracking a few bugs.
You will find full information here:
https://www.youtube.com/watch?v=P9HqMZviaMg&list=PL0M0zPgJ3HSftTAAHttA3JQU4vOjXFquF&index=0
RC2 will be released in mid-May.
According to ASP.NET Core installation guide:
Before you start
Remove all previous versions of .NET Core from your system.
To do this use Add/Remove programs in Control Panel (Windows).
RC2 you can download from: .NET Core Downloads
Yes, it has been released! You can find the various downloads at: https://www.microsoft.com/net/core
I've read that STS 3.6.0 is based on eclipse Luna. However, I have STS 3.6 (upgraded from the IDE since several versions ago) but in the "about" section it says the Platform is Eclipse Juno SR2 (4.2.2).
Is there something special I have to do to upgrade my STS to eclipse Luna and so be able to use Java 8, and Tomcat 8?
If you update STS using the "Check for Updates" mechanism, it updates to newer versions of STS, but it doesn't update the underlying Eclipse platform version. This is by design to avoid complicated situations with conflicting plugin dependencies, etc. Therefore you would need to start with a fresh STS 3.6.0 for Eclipse 4.4 installation in order to jump to Eclipse 4.4 (which also includes the Java8 support).
If you don't want to manually install a bunch of third-party plugins again manually after starting with a fresh STS installation, you can consider to use a script that installs features automatically, like this one: https://gist.github.com/martinlippert/5155155. It is for Mac, but it should be transferable to other operating systems.
Hope this helps!
We’re thinking about downgrading our Alfresco Enterprise 3.4.1 to Alfresco Community.
I’m used to Alfresco Enterprise, but I have no experience with Community version.
We’re using EMC, Alfresco Explorer and our own development based on Web Services API and Foundation API.
I’m worried about database migration. Could I simply configure Alfresco Community 3.4.e to use our Oracle Database for Alfresco Enterprise 3.4.1? Is the schema compatible for both Community and Enterprise distributions? Which version of Alfresco Community should I use? 3.4.e? What is the downgrade path between distributions? Is there any kind of correspondence between versions of both distributions?
Any downgrade experience, guide or any related information will be welcomed.
The Alfresco Community Edition is open source, and works with a fully open source stack. Your DB options are PostGreSQL (recommended) or MySQL.
Alfresco Enterprise supports the open source databases that Community supports, PostGreSQL and MySQL, as well as a few proprietary databases too. You can look at the Database Configuration page for more information. Support for Oracle databases is only available in Enterprise.
If you want to keep paying Oracle all that money for your database licenses, then you'll need to continue to pay a tiny fraction of that cost to Alfresco for an Enterprise License. Community, being open source, only supports a fully open source stack, so you can't use Community with your uber expensive proprietary database!
If you were using an open source database like PostGreSQL or MySQL, then you might be able to do the switch as part of an upgrade. Enterprise Service Packs (eg 3.4.1) are normally newer than the equivalent community release from that series (Community gets the bug fixes on Head). Moving from a 3.4.x enterprise service pack back to a 3.4 community wouldn't be recommended, but moving from 3.4.x enterprise to a 4.x community might work. However, that's not a tested migration path, so you could well be on your own... Alfresco QA tests community -> newer community, enterprise -> newer enterprise, and community upgrading to enterprise, which are the supported paths.
This question is similar with this one about difference between Community and Enterprise version
You can not use Oracle database for Community version. It is only available for Enterprise.
There is not downgrade path for any Alfresco versions. If you are using Enterprise 3.4.2 try to use the same Community version.
I searched the web for possibilities of a downgrade from enterprise to community version, too. What I found is the answer "You may be able to downgrade, however that is never supported or tested."
When downgrading, you have to keep in mind that the community version X usually has more functionalities than the enterprise version with the same version number.
So, downgrading is experimental. I have already seen log files where the downgrade failed.
Maybe it is an option for you to export all content and import this ACP file on the new system with the community version?
Please read your contract carefully. Support and Licensing might not be the same thing in your case. If you don't want to pay anymore to Alfresco, you might be entitled to keep using your current enterprise version, but you would not longer have support. Before considering downgrading, check your contract. If in the future you want to get support and upgrade again, it might just be easier to do it with your current Alfresco Enterprise version.
But, as I said, it depends on your agreement with Alfresco.
Migration of the Alfresco repo database is no fun at all. There is no official way switching databases and in 3.x version you may have serialized objects which could be stored by hibernate db specific. This changed a little when Alfresco removed most of hibernate dependencies after 3.4. It may be an option to migrate to 4.0 EE first, migrate the db to postgres (which is closer to oracle than mysql) and finally upgrade to Alfresco Community 4.2.f (latest version with Web Services API). This may be a lot of work (even in your code) but should work.
Here in Germany it is legaly problematic to limit software usage in time if you sell a support subscription (at least for the old contracts you may have) so customers here can request support for a time unlimited EE license key before canceling the subscription contract. I recommend you go this way and update your old 3.4 to the latest 3.4.x or 4.x enterprise version available and stay on Oracle db if you don't care these costs. This step should be done anyway ;-)
I have done it before in order to create a development environment in my local machine,
First, you cannot use Oracle database so you have to use postgresql (recommended) or MySql, exporting and importing the database is not recommended, so you have to create the repository hierarchy and fix the rules, etc., then copy all custom jars (jobs, actions, workflows...) and library from the lib folder to the new one,
If you are using an external application based on alfresco uuids, make sure you updated the uuids after creating the repositories and rules