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!
Related
What I want to do: Upgrade to the latest core and standard versions for my apps and libs that the apps depend on. These apps and libs are currently on 2.2 (latest) and .Net Standard 2.0 for libs.
What have I tried: I have installed the latest versions of all the SDKs, runtimes and the latest IDE of 16.3.2 - I want to attempt to target .NET Core 3.0 and .NET Standard 2.1 for my libraries.
I cannot do any of these things either directly, or by manually messing with project files. It is not in the dropdown for existing projects and if I manually edit the project file, I get an error saying that 3.0 is not a valid SDK version.
If I spawn a new IDE and create a new web app, console app or class lib, I can easily target 3.0, or NetStandard 2.1 - which is fine and proves that it's all installed... but what I don't understand is how to plot a path to migration/upgrade - creating brand new solutions and projects and attempting to recreate the software isn't really an option.
Am I missing something here? The Internet is only really useful for guiding people to how to turn on .NET Core 3 back when it was a preview version, which obviously is no longer the case.
There must be a set of steps to help people migrate from 2.2 core or 2.0 standard ...
If you stumble upon this and wish to know the answer to this scenario, it lies in a file called global.json - a file which may not be part of your solution that is probably hiding in the root folder somewhere.
Change the SDK version in this file to 3.0.100 (run dotnet --list-sdks in a terminal to find the version strings) and you should be good to go.
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.
Presently our application has been deployed in Alfresco 4.2.2 Enterprise version.We want to move our application to 5.x Alfresco version.
What are all versions released so far in 5.x?Initially I want to test our application in all 5.x Community Versions that are released so far.Where can we download old & new 5.x Community Versions?
What are the new features added in 5.x w.r.t 4.2.2?
You can find the community versions here : https://sourceforge.net/projects/alfresco/files/
The current enteprise version is the 5.1. The previous version was 5.0.3.
About the new features, I encourage you to look at the different releases notes because I don't know what you are looking for.
The biggest change for me is the disappearance of the alfresco legacy backend, the end of lucene and the refactoring of some apis.
When developing an ASP.NET 5 app, I can install the mono runtime into it via NuGet. For example, the latest to date dnx-mono.1.0.0.rc1-update1.
As far as I've tested, the thing is the actual runtime I'm installing on, for example, Linux via DNVM tool to run ASP.NET apps on it.
If I installed the package into a project, I can't then chose it in project properties, nor I can chose it when publishing into a folder - only Windows clr versions are available.
So what's the point of installing it right into the application project?
Or maybe it is not intended to be installed into a project, but exists solely for DNVM could find and pick it up?
You're right. It is used by DNVM and your application should never reference it directly.
I have the unfortunate task of fixing a legacy ASP site that was migrated to Windows Server 2003, and I know nothing about ASP. The main issue appears to be with ASPSmartUpload, of which I have version 2.3 installed. According to http://foradvice.net/smart_upload_faq.htm:
FAQ: does aspSmartUpload work on
Windows 2003 server ?
Yes, last versions of aspSmartUpload
work fine on the Windows 2003 server.
If you upgrade your OS and used an old
version of aspSmartUpload, you have to
download and setup aspSmartUpload
3.2+.
Of course, aspsmart.com doesn't respond and any Google result for "aspsmartupload 3.2" points to the dead link. The latest version I can find anywhere is v3.0, on some dodgy-looking DLL download site.
What is the best way to resolve this, or can anyone provide a working link to version 3.2 of ASPSmartUpload? Thanks!
We searched for quite a while before finding these dlls.
Here is the link for the ASPSMARTUPLOAD.DLL Usage page that tells you how to install it and a link for downloading version 3.3.
From what I understand, windows server 2008 requires version 3.2 or higher, but we couldn't find version 3.2. I believe version 3.3 will work the same.
One other item, we had to get msvbvm50.dll VB Runtimes for this to work on windows server 2008.
Once these files were registered the server restarted we got past this issue.
Fortunately I have a copy of the original v3.3 distribution.
I've shared it here.