Is there an easy way to migrate sencha command packages to open tooling packages? I tried to use the ext-gen migrate command but this did not work because there is not workspace.json in an sencha command package.
I also noticed there is no way to generate an open tooling package template like you can in sencha command. sencha generate template XXXX.
Is there a difference between an app and a package in new open tooling? Is everything a package?
thanks.
There's no easy way to migrate a package or workspace - only individual applications. The only way that works is to create a new package and move the code in manually.
And, yes, everything is now a NPM package. You'll need to learn that to work out how to package, share, and distribute your code. I can't help with that, as I'm still trying to learn it as well.
Related
I have a Wix installer project for my WPF application, and I am trying to integrate this project into my CI/CD pipeline (Github Actions). Currently, I don't know how to build this project on the build server. The Wix documentation says that I could just check-in the Wix tooling with the actual source code, but this seems like a bad idea. What is the most recommended way of building WiX projects on Github Actions or more generally on a remote build sever?
GitHub Actions Windows environment already has WiX installed along with VS.
So to build your WiX projects (*.wixproj), just use the typical MSBuild command msbuild A.wixproj.
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.
When i had create my project i didn't know abuot create-react-app, but it's really good tool to reduce time that i've spending on webpack support.
Is there a way to migrate whole project to CRA?
First of all, you need a plan to migrate.
As i see, easiest way to migrate it's create new project with create-react-app and just paste your project src to the new place.
But there is figuring out few questions that you need to be ready to handle:
Is your test wrote on jest? If not, you need to migrate them.
Are in your project imports written in commajs style or es6 (import or require)? You need es6 style.
Are you using npm or yarn? CRA recommends yarn.
I have created two apps using 'Visual Studio Code' and 'node.js.' I run them using command 'npm start,' and they show in the browser. I want to build them or deploy them so they can be used by anyone. It says there to use command 'npm run build.' How to do that, and what technique you use in order to build them?
It depends on what configuration you used for building the React app. If you used create-react-app, npm run build is the correct command for building it.
If you used a different configuration (e.g. webpack), you should use the relevant command for that configuration.
Either way, deploying it will be as easy as copy/pasting the build folder's content to the server you want to host it, after running the build command.
Visual Studio Code or any other Code Editor for that matter is not relevant. You can develop, build and deploy any React app using any Code Editor you want, it's just a matter of preference.
"Building" refers to the task of preparing (transforming, minifying, compressing, etc.) all the relevant project files so that they're ready for production (assuming that your build scripts are configured to do so).
"Deploying" an app is usually a separate task that will deploy (upload) your current project build to a development platform provider like Firebase, Netlify, Azure, etc. Note that you have to register with a provider and setup a new project on their end before your deploy your project.
Which provider you use is totally up to you. Also, you have to configure your current project once you've chosen your development provider. They'll provide instructions on how to deploy your project.
On a side note, keep in mind that you can configure your own npm scripts so that they run whatever you want. More about that here
I've started learning React with Redux and part of my development has seen me want to use the Material UI to make my application more interesting. I created my project in Visual Studio 2017 using the React with Redux template for ASP.NET Core.
I followed the documentation presented at the MatrialUI site and opted to use the CDN option for delivery of the MaterialUI library.
I started creating a few elements and was quickly confronted with the message that I needed to upgrade my react installation to use the Toolbar.
My question is, when we use the Visual Studio React/Redux ASP.NET Core template, how do I update my react installation? Is that carried out via NPM? I can't see any nuget packages relating to React.
Many thanks
Hey not sure if you found an answer yet but here is my take:
I tried using npm update inside the "ClientApp" folder, but that didn't seem to work. Something that did work though was manually updating each package. So open up a separate terminal -> cd into the ClientApp directory and then
npm i <package name>#<newest version>
so an example would be
npm i react#16.8.6
Some packages you will definitely need to update are React, React-DOM and rimraf. But you might choose to just update all of them while you're at it. When you're using ASP.NET Core try and go for the 2.2 version, which at least already has Bootstrap 4 installed.
Another tip: With Visual Studio, if you hover over the package names in the package.json file inside, it will show you the latest version. That's gonna make it a bit easier to find out what version you want to update to.
Hope that helped! And if anyone has a better solution please let me know.