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
Related
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 have a .Net Core v2.2 project and I set the Publish options as follows:
I also set the Package information:
Also modified the .csproj file as follows:
The Details of the generated(?) exe looks like this:
What else should I set to make those informations appear not only in the dll file but in the exe file as well?
UPDATE
According to the possible answer, there is a fundamental change in the upcoming version of the .Net Core SDK starting with version 3.0. After verification, this question and answer will help solving the issue instead of providing an explanation of why it can't be done.
What else should I set to make those informations appear not only in
the dll file but in the exe file as well?
I updated my Visual Studio 2019 to version 16.2.5 (latest is 16.3.1) and installed the new .Net Core 3.0 SDK. After that the generated exe contains all the version information and can be used as expected.
SDK download link.
This is a simple question.
I am advised on this page that to upgrade an existing project to asp.net core 1.1 I need to download the .NET Core 1.1 SDK.
I am directed to go to this page to download .NET Core 1.1 SDK. It says .net framework/.net core/ Xamarin. I click on .net core option in the middle.
I then click on option "current" and leave "SDK" as is.
It says at the top .NET Core 1.1 SDK - Installer.
I click on the x64 option for windows and get "DotNetCore.1.0.1-VS2015Tools.Preview2.0.3". This is not what I was expecting.
So where is the Dotnet 1.1 installer or have they not labelled this correctly? ...or is this the correct file anyway?
That download page is a bit confusing. When you get to the download page you'll see tabs saying LTS and Current. Click the Current tab to get to the 1.1 download. "LTS" stands for 'long term support' and refers to a released version (1.0.*) that Microsoft is going to support for a while.
Can an ASP.Net 3.5 site run on a server with ASP.Net 4.0 on it?
On the server it has the 4.0 ASP.Net framework installed on it but the site I am making is for 3.5. Do i need to have 3.5 framework installed too to make the page work?
Yes, it does, but in all likelihood, the 3.5 framework should already be installed. If not, ensure that it gets installed.
However, it's usually best to install the versions in order... I have had issues in the past when 4.0 was installed first and a "lesser" version afterward, or when 2.0 was installed before 1.1. It's just good practice to install them in the correct order.
All .net framework installers include the previous version including the service packs.. well they do if you download them directly from microsoft's website which ensures its the newest version.
I've never installed multiple version (1.1, then 2.0, then 3.0 and soforth).. always just the newest and I've never encountered a problem. However if you do get issues that approach might be helpful.
what are some things i should be aware of before i begin this project? i've notice a few differences between this 1.1 site and our 2.0 sites: i noticed that every code behind file has a "Web Form Designer Generated Code" region which i'm guessing i won't need to transfer over to the 2.0 site.(?) There's also a "sitename".dll file in the bin folder which i was told is also a 1.1 thing and that dll file won't need to be transferred over to the 2.0 site.(?) at this -LINK-, the second answer mentions that my new 2.0 site should be created as a Web Application Project and not a Web Site project - does this apply to all 1.1 to 2.0 upgrades and should i consider doing this?
i would appreciate any advice at all on a 1.1 to 2.0 upgrade that you have. i should also mention that i am not allowed to upgrade to either 3.5 or 4.0 - it has to be 2.0. thanks.
2.0 brought a new project type for websites which, in the simplest terms, does not produce a dll for the website like 1.1 projects would. There was a patch released that supported the 'older' project type if you really hated the new website project (which I did).
To be honest I did not have that much trouble converting my sites over to 2.0 way back when it came out. Visual studio automatically converted my projects and I only had a few bugs to work out to be honest.
Try using the automatic upgrade (simply open the project in visual studio 2005 after you install 2.0) and see if you have any issues.
Be sure to install the latest service packs and be sure to test, test, test. .NET 2.0 added some fixes that amount to breaking changes in .NET 1.1. You may run into them especially in the area of XML processing in general, and XML Serialization in particular.
Note also that .NET 3.5 is nothing more than .NET 2.0 plus some additional assemblies that your code does not use. There is no good reason to not upgrade to .NET 3.5 SP1.
There are potential reasons to not upgrade to .NET 4.0, though not very many.