Code Upgrade tool error - version

We are trying to upgrade the site from Kentico 8.2 To Kentico 9. In this there is lot of custom code.
We are using Code Upgrade tool as mentioned in the documentation to upgrade the code: Please check this
It will be really helpful if you could help us in this.

The error being referenced, the path's format is not supported can typically be resolved by copying and pasting the actual path from file explorer AND wrapping it in double quotes. If your WebsiteFolder and/or the .sln file have spaces in them, it will error out unless wrapped in double quotes.

Have you changed the file structure of your project? Have you changed the name or location of the CMS folder? What I would try is to install clean K8.2 installation, hotfix it to the same version you have and copy the "CMS" folder from your project to the clean install and see if it makes a difference.

Related

How to install cinterop tool in Windows/Ubuntu

I am following this tutoriel to use C library in Kotlin (Android Studio) https://jonnyzzz.com/blog/2018/05/28/minimalistic-kn/ But I can’t find the how to install/download the cinterop tool both in Windows and Ubuntu I have the error “cinterop: command not found” ! Does anybody please knows how to install cinterop ? Thank you in advance
This tool is a part of the kotlin-native distribution, and it does not make any sense to use it without the Kotlin/Native compiler. So, in fact, you would like to get all the distribution here, and install it correctly.There are three main approaches to the Kotlin/Native installation. All of them are described in the documentation.
Installing it with the IntelliJ IDEA. You should just get an IDE and let it install everything on its own. It will download all tools and put them to the following location: ~/.konan/kotlin-native-prebuilt-<osName>-<kotlinVersion>/bin/. Then you will be able to add this folder to your PATH and call the tool from CLI.
Installing using the Gradle build system. Quite similar, but this one will require manual installation of the Gradle. The first run will also download all tools and pack them to the same location as in the IDE case.
Installing the CLI tool. This looks like the most appropriate way to follow the tutorial, but won't help a lot when you start working on more sophisticated projects. In general, you should just download the latest version of the Kotlin/Native, unpack it to some folder and add this folder to your PATH.

Install.aspx file issue while upgrading Evoq Content

Currently my application is running on Evoq Content 7.3 and I was trying to upgrade it to Evoq Basic 8.5. I have copied the upgraded file into my application directory And now when I try to access the http://MYWEBSITE/install/install.aspx?mode=upgrade , It is giving error "resource can not found Requested URL: /install/install.aspx.
Please advise.
This looks like some files were removed from the install directory, probably as part of a security precaution. I'm not sure why they were not added back with the upgrade package.
You might be able to fix this by copying the install directory from an appropriate install package. Just the install directory.
As always, make a copy of your database and complete file directory first, just in the event that what you do fails.

Using Quick Install in Visual Studio doesn't actually add the packages to your project

Hello I'm trying to use the Visual Studio extension Quick Install Package to install packages via bower and npm. One example is angular-loading-spinner
When I give the command using the interface, I see that the package.json file is updated and or the bower.json file is updated with the package dependency, but I'm still unable to actually reference the packages as instructed in my html using the tags. No actual files are added to the project, so I feel like I'm really missing something here, or simply don't understand what this package installer is actually meant to do. There doesn't seem to be any clear tutorial on this I can find online, or any good information. It just all assumes it works fine. Can anyone please advise? Thanks]1
Mike, I'm glad to know that my answer was the correct. For future users that have the same concern, they need to look at the folder node_modules to find out all the libraries installed.
This was put in the node_modules folder as pointed out by Jonathan Brizio. The issue was that the files were hidden and had to be included in the project.

How to solve "Build:Unknown compiler option 'listemittedfiles'." on visual studio 2015 update 3?

After updating the NuGet Type Scripts packages, I was facing with one common build error problem "tsc.exe exited with code 1". After searching I have found the solution how to resolve it. As suggested I installed another two NuGet packages named Microsoft.TypeScript.Compiler and Microsoft.TypeScript.MSBuild. After installing those the tsc.exe exited with code 1 problem solved. But in the mean time a new problem arise on build "Unknown compiler option 'listemittedfiles'".
I was trying to solve it by the suggestion of this Typescript build failure.
But still there has no improvement of this problem.
Can anyone be able to provide a solution please? Please take a lots of thanks in advance.
My client project structure is looks like the image Please click here to view the image
I suggest you to try to fix this issue by installing TypeScript 2.0.6 using the following link:
Visual Studio 2015 TypeScript Tools (2.0.6 at the time of writing)
This will also point MSBuild to the proper TypeScript build, which fully supports the --listEmittedFiles command switch.
See also this answer and/or this blog article I wrote on this topic for further details and references about this issue.
I had the some problem. I found out, that I had a wrong (i.e. older) version of typescript installed (in addition to the current one) and even though the latest version was installed too, the old typescript compiler (tsc) was used.
Open a windows console and run the command following command:
tsc -v
The result should be:
Version 1.0.1.0
If you have the latest typescript installed but don't see the version above, you probably have older versions of typescript installed, that may be the cause of your problems. Uninstall the older versions via "Programs and features" in the control panel of windows.

how to package install version of dotnetnuke from source of it

I changed source of DotNetnuke (a little!) and I want to package an install version of my new DotNetNuke.
How Can I do this?
p.s: I know It's not recommended to change the source but I have no another option
(Telerik calendar do not support my date format and I have to replace it with another calendar !)
Thanks in advance
Answer depends on what you have changed, but the simplest way is to deliver patch that should be installed after normal dnn installation. For example, if you have only changed dll, you can ask to follow normal dnn setup instructions and finally relpace dll. If it's more than on file, you can review how dnn upgrade package is built. It follows same folder structure and places only changed files. So if you have couple of dlls changed in bin, the will be placed in bin folder, and if you have changed some ascx file it should be placed in same path by creating same folder hierarchy.
You can also create a package that can be installed to deploy your changes but for smaller set of files it will be complecated.
Let me know if you need more help.
You can package any change into a DNN install package by including the compiled files along with a DNN Manifest file. This can then be installed via the Extensions page. A manifest file is an Xml file which controls where the contents of an install zip are installed. You can make it as simple or as complicated as you need. You can also include xml merge statements to make changes to the web.config file upon install and uninstall. See the wiki for reference : http://www.dotnetnuke.com/Resources/Wiki/Page/Manifests.aspx
Incidentally, you may have been able to deliver your modified telerik source as a separate provider, and configure it via the web.config, thus saving you from modifying the source code. To do something like that, you would build your own module, and plug it in and replace the standard Telerik references.

Resources