I was thinking this would be part of the cloud offering but I can't figure out how to do it.
Is the only way to import into Studio from Visualizer to use a local copy of the Visualizer project file?
It looks to be very good feature. But currently kony is not providing this feature.
Related
I'm trying to add CI/CD to talend jobs (Talend ESB 7.3.1 Open Studio), I saw a few resources specially on the talend community website to do so, but on all of them they used the Talend CI Builder, but i can't find it. In one of those ressources it is told that it is embed in the studio files since v7.1.1
The builder is supposed to be installed here :
but I can't find it in my studio files
Is it because I use an open studio version of talend or the installation directory changed in the v7.3.1 ?
Thank you.
Find the answer by myself, the talend ci builder is only available on the cloud version.
Please note that I am new to front-end and back-end Web API development.
I am not sure if this is possible, and I suspect it is not, but I am wondering if anyone knows whether or not it is possible to modify a .NET CORE Web API with both Visual Studio Code and Visual Studio Community? I suspect it is not because VS Community creates the project with a solution files whereas VS Code does not.
The reason for doing this is that I like the CLI nature of Visual Studio Code to create .NET CORE Web API's that can be developed in tandem with a EmberJS front-end framework. However, I much prefer Visual Studio Community's debugger and intellisense for more advanced development of the back-end. This is purely a preference and not necessarily a show stopper.
Update:
If it is possible, can you please provide the series of commands I would need to issue in order to create a dotnet webapi and add it to a dotnet sln?
Update 2:
The dotnet CLI website does not show how to add a dotnet webapi project template (with a corresponding solution file), which provides a base set of files to create the Web API. From what I can tell, we can add individual files (i.e., *.csproj). Is there a way to create a dotnet webapi project template with a corresponding solution file all at once; or do I have to either add each file manually in VS Code or just create a Web Api in VS Community and then work with it in VS Code?
Reference: https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-sln
Q&A Style:
I am not sure if this is possible, and I suspect it is not, but I am wondering if anyone knows whether or not it is possible to modify a .NET CORE Web API with both Visual Studio Code and Visual Studio Community?
It is possible. I use VSCode and vim on this: https://github.com/sillsdev/appbuilder-portal (which is a .netcore + React app)
However, I much prefer Visual Studio Community's debugger and intellisense for more advanced development of the back-end.
VSCode has a .net core debugger and intellisense. you may need to install the C# extension.
If it is possible, can you please provide the series of commands I would need to issue in order to create a dotnet webapi and add it to a dotnet sln?
dotnet --help can walk you through this, if you don't feel like looking up docs. Here are the docs though, if you want to bookmark this or somethin': https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-sln
dotnet sln add path/to/project.csproj
Is there a way to create a dotnet webapi project template with a corresponding solution file all at once; or do I have to either add each file manually in VS Code or just create a Web Api in VS Community and then work with it in VS Code?
I think in the CLI, this needs to be multiple commands.
dotnet new webapi
dotnet new sln
dotnet sln add *.csproj
hope this helps
I am trying to make a continuous deployment of dotnet core 2.0 app in visual studio 2017 community as per https://channel9.msdn.com/Events/Visual-Studio/Visual-Studio-2017-Launch/T115
The given options are specified in that video are like this
But when i try
there is no azure container registry and azure container service.
How to specify these two options. Please help.
While creating a project, make sure you Enable Docker Support as shown below.
We are working to migrate to Azure Cloud Services (not Web Site) for our ASP.net Web Application. We are wanting to start using the Team Foundation Service with 'Continuous Integration' publishing like we currently use between AppHarbor and GitHub.
We are running into challenges when using TFS's 'Continuous Integration' feature. The builds are inconsistent when comparing Visual Studio to Azure Cloud Service to TFS to Azure Cloud Service. When we publish to Azure Cloud Service using the TFS's 'Continuous Integration', our static pages work fine but for the pages that have an *.cs extension are not able to find the controls we have placed on those pages. However, when we publish using Visual Studio 2010 to Azure Cloud Service, these pages operate correctly.
Can you offer any insight to why Team Foundation Service's Continuous Integration to Azure Cloud Service would result in pages with an *.cs extension not being able to find the controls we have placed on those pages while a build and deployment using the same exact code from Visual Studio 2010 to Azure Cloud Service works perfect?
Make sure all the referred assemblies that include the custom controls are "NOT" referred from GAC. Ideally put those in a folder (call it libs or references etc to easily identify). Then refer the assemblies from that location in your project, also don't forget to mark them Copy Local = True.
Anything that is not part of the framework should be included like this.
I am using the Jupiter as Visual Studio solution project for a v5 umbraco site -
http://our.umbraco.org/projects/developer-tools/jupiter-as-visual-studio-solution
however i'm struggling to find the project to use for v4.x Does anyone know if it can be accessed anywhere or if i can easily recreate?
You can still access the Umbraco 4.7.1.1 downloads here.
If you don't want/need the full blown source, you may just want to run the 'webdeploy' option as a website in Visual Studio.