If I deploy my app using:
meteor deploy myapp.meteor.com
How can I check the version of meteor running on the remote server?
Simply evaluate Meteor.release in your app code.
Meteor.release is a string containing the name of the release with which the project was built (for example, "0.7.1.1"). It is undefined if the project was built using a git checkout of Meteor.
Also note that every project is pinned to a specific release of Meteor. Demo at http://release.meteor.com/ - note the release is Windows, which is clearly not what meteor.com runs :)
Related
I have a Xamarin.Forms application which targets iOS, Android and UWP. I have built an Azure pipeline that generates my .ipa and .apk files which can be used to install on devices that support its debugging. However for UWP I am trying to generate a build that will allow side installation (not for the app store), but not sure how to do this.
In visual studio there is the option to "create app package" (see screenshot below) which generates a bunch of files including an install.ps1 script. And running this script installs the application on my machine. I would like to automate this process in my Azure Devops pipeline but not sure how to. Any help would be appreciated.
Figured out how to do this.
I used the following MSBuild Arguments in my Build solution Task:
/p:AppxBundlePlatforms="x86|x64|ARM"
/p:AppxPackageDir="$(System.DefaultWorkingDirectory)\AppxPackages\\"
/p:AppxBundle=Always
/p:UapAppxPackageBuildMode=SideloadOnly
/p:AppxPackageSigningEnabled=true
/p:PackageCertificateThumbprint="$(UWPThumbPrint)"
/p:PackageCertificateKeyFile="$(UWPCertificate.secureFilePath)"
/p:PackageCertificatePassword="$(UWPCertificatePassword)"
$(System.DefaultWorkingDirectory) may be replaced with $(Build.ArtifactStagingDirectory) if you are using an Azure machine. See this link for information on Build Arguments.
I am then able to archive the contents of $(System.DefaultWorkingDirectory)/AppxPackages with an Archive task.
I am using visual studio 2017, created a new xamarin forms project and tried to run the UWP project. It shows the following error:
the project needs to be deployed before it can be started. verify the project is selected to be deployed the solution configuration manager, or deploy it explicitly by clinking one of the deploy commands in the build menu.
I have looked at all online solutions and only found that you need to set the cpu to x86 and to check the deploy checkbox under the configuration manager under the solution. Both these options don't work. I still get the same error. I have also tried every cpu option including ARM.
Have you tried to uninstall the existing UWP app from the Windows Start menu > All apps? Then deploy again from VS. It did the trick for me.
Sometimes when I create an app packet for win store; Visual studio seem to get hung up building to the packet (project needs to be deployed before it can be started -error).
I solve it by creating a new app packet.
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).
After adding mobile platforms, meteor build will automatically build all the mobile platform and the backend server.
Is it possible to only build the backend server?
Unfortunately the build feature doesn't do this.
There is a deprecated meteor bundle feature that still works though:
meteor bundle app.tar.gz
Builds a app.tar.gz bundle containing the server bundle.
Yes just give it parm --server-only to skip mobile client code
as in
meteor --release x.x.x build --server https://example.com --directory /my/bundle/foobar --server-only # replace x.x.x with your meteor release
I know this works because I use this technique in the process I built to rebuild my entire webapp and this is working in production just fine.
I am trying to run my meteor.js app using the latest 0.8.0-rc1 build. How do I update my app to run with 0.8.0-rc1
The current release is 0.8.0-rc3 (2014-03-26). You can update your app by running meteor update --release 0.8.0-rc3 in the app root directory.
Additionally, here are two great resources for running a Meteor.js app on blaze (0.8.0)
http://meteorpedia.com/read/Blaze_Notes
https://github.com/meteor/meteor/wiki/Using-Blaze