I have several cApp projects in Eclipse/Carbon Studio 1.0.14. Is there an "easy" way to migrate these to Developer Studio 2.0.0. If so, what's the best way to do it other than recreating all the artefacts and new cApp projects.
Also after uninstalling 1.0.14 and installing 2.0.0, my cApp projects are not recognized anymore as cApp projects.
Thanks and regards,
Danny
Currently there is no way to migrate other than recreating the projects with new Developer Studio 2.0.0.
We are planning on implementing a migration application which allows users to convert 1.x.x applications to 2.0.0 compatible versions. But we are unable to provide any solid timeline when this tool will be released.
Thanks and Regards,
Harshana
Related
I am trying to setup Visual Studio 2017 for Django Development but the Django (1.9) version is old, How can I update it to latest version (>= 2.0).
Create a Django Web Project with proposed install. Name Your Env.
choose "Python Environment"
choose your Enviroment
choose Packages (PyPi)
choose available Updates
Hi you can go through this link https://djangobook.com/developing-django-visual-studio/ this is a complete setup guide.i hope it helps.
I tried to add jquery to an asp.net core project using NuGet Package Manager of Visual Studio Community 2017 (version 15.5.2), but there is no jquery js files added to my project. Here is the screenshot:
Tried with Bower Package Manager, then the files are downloaded to bower_components folder but not to wwwroot as many people said.
Same thing for jquery-ui, bootstrap, etc.
Anyone experienced the same problem. Is there any work-around?
BTW, this accepted solution doesn't work for me: Where are jQuery-UI scripts stored in MVC6 project?
For ASP.NET Core in Visual Studio 2017:
NuGet shouldn't be used for client-side libraries.
After that Bower was used for this purpose, but now it is deprecated.
Currently the supported tool for managing client-side libraries is LibMan. Here is very good explanation how to use it in VS2017.
I have been trying to install the Azure Functions and Web Jobs extension, however installation fails. Looking through the error log it appears that the piece that isn't working is this:
Install Error : System.InvalidOperationException: Installation of Azure Functions and Web Jobs Tools failed. To install this extension please install at least one of the following components: Microsoft Azure WebJobs Tools
I think that the problem is that it is looking for itself with the wrong name (Microsoft Azure WebJobs Tools instead of Microsoft Azure Web Jobs Tools). Is there any way to fix this?
Just had the same problem and the error was not very helpful :( Fixed it by installing the Azure Development "workload" from the Visual Studio Installer. After running the installer, you can choose to modify the installation and add this. It will actually come with the extension you're trying to install, oddly enough, but it will not be the latest version of it.
Here is an image which I hope helps:
After installing latest update for VS2017, I lost almost all the project templates for starting new project. I get following message when starting new project.
I uninstalled and then reinstalled some “Workloads” using new installer without success.
After searching web for solution, I tried to install “NuGet Package Manager” using Extension manager, but seems there is no NuGet Package Manager for VS2017.
Any jugar/solution please?
Repairing VS2017 solved the problem. Is it not a very long route?
I installed wso2 carbon studio 2.0.1 (ref: http://wso2.org/project/developer-studio/2.0.1/docs/install_guide.html, https://wso2.org/jira/browse/TOOLS-739), but root-artifact.xml does not automatically generate when CApp project creating. And a pom.xml file has been created over here. Could I build a root-artifact.xml manually?
WSO2 Developer Studio 2.0.0 and later versions no longer uses the root-artifact.xml and the previous C-App model.
There are fundamental changes between Dev Studio 2.x.x versions and 1.0.x versions such as dropping root-artifact.xml, introducing pom.xml and using pom.xml for metadata management, new project structure, etc.
So it is not a bug in Dev Studio 2.0.0 but rather how it is designed.
well, wso2 carbon studio v1.0.14 is working. It seems a new bug for v2.0.1.