We have created our Teams FX project using Teams Toolkit v 3.7.0 and we have already released our app to the production.
TeamsFX CLI version from package.json: "#microsoft/teamsfx-cli": "^0.14.0",
TeamsFX API version from package-lock.json: "#microsoft/teamsfx-api": {"version": "0.18.0",
Now, we would like to upgrade the project to latest version. I have gone through wiki articles but it's not very clear. Can you please let us know the upgrade procedure. Is updating the Teams toolkit version to latest version enough or any other additional steps required.
Please let us know.
Thanks.
Latest VSCode teams toolkit extension or teamsfx cli already support migration.
If you're using VSCode, you can open the project, then you will see the dialog as below, click upgrade, it will automatically upadte your project to latest version:
If you're using TeamsFx CLI, you can run preview or provision command in the project, then it will ask you to upgrade app:
Tip: due to there is a bug for upgrade in recent version, recommend using latest version 4.0.5 to avoid migration issue.
Related
I installed the .NET SDK 2.1.301-win-x64.exe and afterwards updated all the nuget packages to 2.1.1.
In my WebApp I have the Nuget Package Microsoft.AspNetCore.All 2.1.1 and Microsft.NETCore.App 2.1.0. In the Nuget Window I see that there's also the Version 2.1.1, but I can't select it (Blocked by Project)
Same story in my Console App: Microsft.NETCore.App 2.1.0
My first question: Is here already something wrong? Or is this expected behavior?
If I build the WebApp as self contained App, that works well.
If I biuld the Console App as self contained App (Self-contained / win-x64). I get the follwoing Error:
The project was restored using Microsoft.NETCore.App version 2.1.1,
but with current settings, version 2.1.0 would be used instead. To
resolve this issue, make sure the same settings are used for restore
and for subsequent operations such as build or publish. Typically
this issue can occur if the RuntimeIdentifier property is set during
build or publish but not during restore."
The source of this error is a referenced project.
What do I do wrong? Let me know if you need additional information, then I will add it.
This is a known issue for the moment. In your referenced project's csproj file, set the TargetLatestRuntimePatch property:
<PropertyGroup>
<TargetLatestRuntimePatch>true</TargetLatestRuntimePatch>
</PropertyGroup>
This only happens when a .NET Core application references another .NET Core application and self-contained roll-forward only partially kicks in during publish.
For portable applications, it is enough to target 2.1.0 version of Microsoft.NETCore.App and when run on a target machine, the latest patch available on the machine will be used automatically. In recent tooling, a change was made so that the tooling would use the latest known patch version for self-contained applications so you automatically bundle the latest patch release with your application. However, this doesn't flow over project-to-project references.
See Self-contained deployment runtime roll forward for more information.
I have installed the dotnet core sdk and it all works. I want to update the nuget version though so that when I run dotnet pack it uses the latest nuget. With normal nuget.exe I can run nuget.exe update -self and it updates itself. However with dotnet cli there doesnt seem to be any equivalent command. I also cant find which nuget.exe path its referencing to update it there manually.
Any ideas on where its located or how to update this? Or do I need to just update the entire .net core SDK to get a newer nuget version?
I am pretty sure you can't upgrade the nuget version shipped in .NET Core. It's a core part of the .NET Core SDK and no individual component of SDK can be upgraded.
Why do you want to use a newer NuGet version?
I had installed VS2017 Professional last year which came with ASP.NET Core version 1. I wanted to use features of Core version 2 so installed the latest SDK. Now in my Command line when I check version dotnet --version the it comes fine. Means it is Installed.
But when i try to start the a new project then the framework list it gives does not contain version 2 templates.
Please can anyone help me with it?
You will need to update your Visual Studio 2017 version. Latest is as of today is 15.5.6.
Hi I installed Visual Studio Tools for Apache Cordova during the winter. I have now worked on an angular project which has npm dependancies, and gulp files which use a Node server to serve pages to test out the app.
I did however like the way VS.Net installed NodeJS and other tools during the Visual Studio Tools for Apache Cordova installation, adding the correct paths to my system to get great CMD support for git, npm etc.
I want to continue to develop Cordova apps using Visual STudio, especially using the Mac remote deployment node module that was installed. However I find that the version of NodeJS and NPM that was installed is now out of date. I got a warning about version numbers when I installed the Azure-cli node package.
What is the best way to update NodeJS and NPM versions so that they stay integrated with Visual Studio Tools for Apache Cordova
There is no specific limitation for updating nodejs, but please be aware of some known issue related to newer version of nodejs. Just make sure you will not run into these scenarios, and I think you can feel free to update.
If you do encounter any issue after you update the nodejs to a specific version, I think it's good to raise the issue and let MS VS team to fix it in future release.
And make sure the nodejs is added into your PATH system environment varaibles.
I am seeing facebook cordova settings issue after upgrading the Meteor framework from 1.0.2 to 1.0.4 version. Please let me know if anyone has seen this issue before?
meteor run ios
"Meteor settings for accounts-facebook-cordova not configured correctly"