Update folder structure in VS Tools for cordova to support CLI interoperability (VS2015RC) - visual-studio-cordova

I see that VS2015RC support the more cordova suggested folder structure, and CLI interoperability. Are there any docs that describe how to modify existing apps to use this new feature? I've build an app based on this the VS2013 ionic starter template and would like to start using the ionic cli.
Thanks for any suggestions.
Larsi

This documentation describes how you manually convert your existing apps to VS 2105 RC project structure. Let me know if you have problems accessing the documentation.

I don't think the docs for this are available yet, but this post (under Method 2) walks through getting the CLI project into a VS2015RC TACO project...
Using Ionic with Visual Studio Tools for Apache Cordova
In general the steps are...
create a Cordova project using CLI
create a 2nd (empty) project using VS2015 RC Cordova (blank app) template
from the VS project, copy the \merges, .jsproj, and taco.json to the CLI project folder
Open the .jsproj and cross your fingers :)

There is another method I believe, which I have used -
Create a new Blank App using VS 2013/2015
Copy all the contents from your www folder from your existing project and paste it to the www folder of this blank app.
Build and enjoy!

Related

Xamarin.Forms upgraded to Maui - Visual Studio Cannot debug/run?

Application upgraded using Microsoft's auto upgrade command line tool.
Some code fixes, and the code builds successfully.
Visual Studio however does not show me any way to debug my app.
When trying to click on Debug anyway, a random Android Emulator from my list(which is not showing currently)
Will open, but deployment will fail without specifying the reason.
Has anyone managed to upgrade an existing Xamarin.Forms project to Maui?
I managed to make VS recognize the Android project in my converted solution.
I added the <SingleProject>true</SingleProject> property into my Android project's .csproj file under the first/main property group, closed VS, deleted Bin, Obj, .vs folders.
After starting VS again , I rebuilt and VS allowed me to debug on selected .net targets like a single project Maui solution.
This is very strange that it works, since this solution is made of 3 project like in a Xamarin.Forms solution, so it doesn't make since that adding this property solves the issue, but there you go.
Delete .bin and .obj folders. Delete solution's hidden .vs folder. Build. Does it show debug option now?
Try restarting VS (after the successful build). Now work?
If not, Create a new project using Maui template.
Use solution / manage all nugets to add nugets used by your project.
Copy all your source files into that new project.
Project / "Add existing items": all those source files.

How to add an additional Uno head to an existing Uno solution?

I can only find commands how to create and build Uno solutions from scratch but nowhere how to add - for example an additional mobile head ? Neither Visual Studio templates offer it on such granularity.
dotnet new unoapp-net6 -h tells neither anything about such option.
Adding Platforms to an Existing Project
If you have an existing Uno Platform project, and you have not selected all the platforms you need when creating the project, this guide will show you how to add new ones.
Considering that your project is called MyProject, and you want to add the Gtk project head:
In a separate temporary folder, create a new project using the Visual Studio 2022 or dotnet new templates, using MyProject for its name.
Unselect all platforms except Gtk in the platforms selection dialog
Once the project has been created, navigate to the new folder MyProject.Skia.Gtk
Copy this folder to the existing project structure, at the same level as the other platform folders
In Visual Studio, right-click on the Platforms solution folder, then select Add, Existing project
Save your solution
Your new platform project is now ready to be compiled.
platform.uno

Deploying ASP.NET Core App to Google App Engine using Mac Visual Studio?

I am running Visual Studio for Mac and I am truing to deploy my ASP.NET Core App to my Google App Engine project. I followed the steps described in this official guide but I got stuck in the "Install Cloud Tools for Visual Studio" step as there's no extension for Visual Studio Mac version.
I also came across the Cloud SDK for Mac and now I am confused which way to go. What's the relationship between these two guides and what's the right way of deploying a VS ASP project to App Engine on a Mac?
EDIT
app.yaml file contains:
runtime: aspnetcore
env: flex
Steps to deploy to Google App Engine:
Create a new ASP .Net project in Visual Studio
Build your project.
Install Google Cloud SDK: https://cloud.google.com/sdk/.
You’ll have to configure gcloud for your Google Cloud Platform project.
See: https://cloud.google.com/sdk/docs/quickstart-macos.
Run the following commands via terminal while in the same directory as your VS solution file:
gcloud app create
dotnet restore
dotnet publish -c Debug
Create an app.yaml file as follows and place it in the “publish” directory.
The contents of the app.yaml file are:
runtime: aspnetcore
env: flex
The path to the publish directory will be as follows: ".../my_vs_project/bin/Debug/netcoreapp2.0/publish"
Run the following command via terminal while in the same directory as app.yaml file:
gcloud app deploy
Well, the SDK is a lower level tool to use and hence more cumbersome. Basically what "Cloud Tools for Visual Studio" does is hiding the complexities of using SDK. Since there is no GCP extention for VS Mac looks like that's the only choice that you have so you need to do SDK commands like " gcloud app create" and "gcloud app deploy" to deploy your project to GCP. I hope this is helpful.
Note: the comment on another answer indicates that the confusion comes from also looking at the Google App Engine .NET Flexible Environment Documentation.
In general GAE is higher level cloud offering which can take care of some of the maintenance activities a plain, general-purpose VM infra like GCE would require (for example scalability), so you can focus more on your app itself instead.
But the choice of using GAE or GCE is really yours - it depends on how you want to build and use your app. And maybe on how well these are supported/integrated with your tools of choice (VS in your case).

Pre Build Tasks with Visual Studio Tools for Apache Cordova

I am using bower.json to install dependencies for an Apache Cordova app created from Visual Studio and was wondering if it is possible to run a pre build task somehow in VS 2015 using the new task runner explorer (or another way) to copy just the minified files from bower_components to www\scripts or if my only option is what is listed here?
If it is possible using gulp, please let me know how starting form the blank Cordova app VS template.
The Visual Studio guidance for using NuGet with Cordova projects actually has something that may help here. That document includes a note about how to setup a before_prepare hook to copy NuGet files into the www folder when building. In Cordova before_prepare is one hook into the build process that is similar to a Pre Build task.

Configuring existing ASP.NET project for DNVM, DNX environment on a Mac

I have an ASP.NET Web API project created on Windows using Visual Studio. How can I set this up for use with DNX/DNVM (on a Mac)?
Switching to Git solved the source control compatibility with TFS. But I wasn't able to find references to getting a project working across both these development environments.
I'm assuming as a first step the project will have to be migrated to ASP.NET 5/vNext but wondering other problems lurk around the corner with different project members using different environments.
I get an error when I run - git:(master):dnx . kestrel
As you mentioned yes you will have to migrate any namespace changes. I have a project that is developed across both. Also changing csproj files to xproj. Support is coming for some kind of interop between the different project types but its not here yet.
For build, publish, deploy from git without relying on VS publish capabilities or MSBuild you can follow my blog post here.
Basically you use DNU to publish and then kudu to deploy.

Resources