I'm trying to convert a multi-application project (v6.2) into a npm-based with webpack support.
Running ext-gen migrate fails with the error:
Upgrade multi-application workspace is not yet supported
Is it possible to stay on v6.2 and migrate to npm?
What is the correct way to do that?
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'm using .net core 2.1 project with DBUP library, but when I try to run the DBUP inside octopus deploy the migration tool is returning an error System.Data.SqlClient is not supported on this platform.
I followed all these steps from an Octopus Documentations https://octopus.com/blog/dbup-database-deployments...
Already did this steps to fix the problem but without success:
net core SDK 2.1, 2.2 installations on the target server
Restart the server
New release with System.Data.SqlClient nuget package associated with the DBUP Project
Not sure what I can do more to fix this issue
Found the problem, DBUP project needs to be published isolated from other projects.
My bad was, trying to run/use dbupproject.dll file as a reference from other projects.
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
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.
Friends,
I have already setup TFS build on my box. Currently the build can be triggered using VS IDE or Web interface. However i will like to hook existing TFS build process in to Jenkins as we use Jenkins as standard build tools for all platform builds. Is there any plugin available? I searched with available plugins but it has only MS build plugin.
Thanks
Bala
There is a TFS Plugin available & also Jenkin-TF tool available. Check this link, it has been For detailed instructions on how to configure TFS & Jenkins
http://blogs.msdn.com/b/visualstudioalm/archive/2012/10/19/building-ios-apps-in-tfs.aspx