I know this is a simplistic question, but if I have a meteor project using 1.2, and I start a new project and update the new project to 1.3, is my old project still using 1.2, or is the update a system-wide update?
Your project is still going to use 1.2 . Updates in other projects won't affect that. You will have to go to the project's root folder and run
meteor update
in order to upgrade to 1.3 .
Related
Locally, I can build and run my Xamarin Forms application with no issues. In my Azure build pipelines I have my master branch failing because of my target framework version. It says it is 9.0 when it should be at least 10.0.
In my Android project file I have the framework version set to 10.0. I have made sure it is also v10 in the properties tab for the project. Yet I still get the below error.
##[error]C:\Users\VssAdministrator\.nuget\packages\xamarin.forms\5.0.0.2012\build\Xamarin.Forms.targets(188,5): Error XF005: The $(TargetFrameworkVersion) for MyApp.Android (v9.0) is less than the minimum required $(TargetFrameworkVersion) for Xamarin.Forms (10.0). You need to increase the $(TargetFrameworkVersion) for MyApp.Android.
Try to open your .csproj file,and manually modify its targetFrameworkVersion.
<TargetFrameworkVersion>v10.0</TargetFrameworkVersion>
Verify that BOTH of the following project properties are set to 10.0:
Application / Compile using Android version (Target Framework).
Android Manifest / Target Android version.
https://learn.microsoft.com/en-us/xamarin/android/app-fundamentals/android-api-levels
If those are already both 10.0, then make sure the Azure build pipeline has up-to-date versions of Android SDKs and tools.
Another way to fix:
If you are able to create a new sample solution, and successfully build that via Azure, then start a new solution, and add all your files to it.
I have ASP.NET Web Application that is deployed on production already. I had to change the target framework of the project from 4.5.2 to 4.7.2 on my local/source and push the changes to developement to get tested.
The problem I am facing is when I changed the target framework of the project the packages did not 'handle' it very well and I had to uninstall and reinstall them with update-package -reinstall -ignoreDependencies
Everything works as normal afterwards but I will need to commit 99+ changes. I am not sure how to handle this migration between the enviroments. So far all of the changes made in the C# code requred only bulding and exchanging the dll file(copying the one from local to development and replacing it) or direct replacement/add to a new javascript/cshtml file.
How I manage to solve the problem is:
After changing the target framework I had to remap the packages as mentioned above which caused a lot of changed in my source. All I did was to build the new 'version' of the project and get the whole bin folder and replace it with the one of the deplyed project in the server side, also I had to compare the changes in the config files.
What I want to do: Upgrade to the latest core and standard versions for my apps and libs that the apps depend on. These apps and libs are currently on 2.2 (latest) and .Net Standard 2.0 for libs.
What have I tried: I have installed the latest versions of all the SDKs, runtimes and the latest IDE of 16.3.2 - I want to attempt to target .NET Core 3.0 and .NET Standard 2.1 for my libraries.
I cannot do any of these things either directly, or by manually messing with project files. It is not in the dropdown for existing projects and if I manually edit the project file, I get an error saying that 3.0 is not a valid SDK version.
If I spawn a new IDE and create a new web app, console app or class lib, I can easily target 3.0, or NetStandard 2.1 - which is fine and proves that it's all installed... but what I don't understand is how to plot a path to migration/upgrade - creating brand new solutions and projects and attempting to recreate the software isn't really an option.
Am I missing something here? The Internet is only really useful for guiding people to how to turn on .NET Core 3 back when it was a preview version, which obviously is no longer the case.
There must be a set of steps to help people migrate from 2.2 core or 2.0 standard ...
If you stumble upon this and wish to know the answer to this scenario, it lies in a file called global.json - a file which may not be part of your solution that is probably hiding in the root folder somewhere.
Change the SDK version in this file to 3.0.100 (run dotnet --list-sdks in a terminal to find the version strings) and you should be good to go.
I create a new project using VS2017, select new Console App (Core) version 2.1; etc. When I use NuGet to install the Entity Framewwork Core, version 2.1.1, it is not installing to the Assemblies directory but instead appears under the NuGet directory. When I try to add a migration using the package manager I get a 'The term 'add-migration' is not recognized' error. I have reviewed the other SO answers to this problem, and searched google, but none of those helped.
I have another project, it's an older one from several months ago, where the Entity Framework Core was installed under the Assemblies directory and for that project everything seems to work.
From the above it appears that where NuGet places the Entity Framework Core dll is the only difference and it is causing the package manager to fail to find it.
The get-module command for the older project shows the Entity Framework Core and the correct version, but get-module for the new project does not.
Any thoughts on why this is happening and how I can fix it?
From this post :
The solution that worked for me after trying a whole raft of other solutions posted, was to right click on my project => select 'Manage Nuget Packages' => select the browse tab, but thick 'Include prerelease' check box, and install the 'Microsoft.EntityFrameworkCore.Tools'. N.b that aspnetcore project in visual studio 2017 do not seem to have the 'project.json' file.
I have Currently working on NopCommerce Project which is version 2.3 but i want to Convert this project to latest version 3.0. I have already done it this project on version 2.3 .
So how to Convert this project 3.0 Could you please help me step by step explanation i am very disappointed for it.
Note:- Currently working on NopCommerce project version 2.3 (ASP.NET MVC4 Razor),Entity Framework 4.0 and sql server 2008
I have following doubts:-
how to convert current NopCommerce project(version 2.3) to latest version(3.0).
NopCommerce version 3.0 supporting ASP.NET 4.5 Framework. How to convert ASP.NET4.0 to ASP.NET 4.5 this NopCommerce project
Thanks !
Do the following:
Backup your existing database*
Execute upgrade.sql script over your database
Remove all files from the previous version except App_Data\Settings.txt and App_Data\InstalledPlugins.txt
Upload new site files
Copy back App_Data\Settings.txt and App_Data\InstalledPlugins.txt files
Ensure that everything is OK
*If you stored your pictures on the file system, then also backup them (\Content\Images) and copy back after upgrade
Note:
The updatescript can be downloaded trough the following link:
UpdateScript Download