How to publish a NopCommerce website and NopCommerce?

I have deployed the NopCommerce website for Windows azure and I can see the homepage of the NopCommerce website on the website. After logging in using the administrator credentials, I see the administration link at the top. But when I click on the link, the administration website is not displayed.

It seems that the admin is not being deployed from the NopCommerce website. When I tried to publish to the Admin website in Visual Studio on the azure website, this did not work. Can someone tell me how can I deploy an admin site?

+6
source share
7 answers

Run Deploy.bat in the root folder. This will create the entire site structure in the Deployable folder. FTP, which is up to your site.

+4
source

It's quite complicated, but it will make sense to you after getting used to NopCommerce.

You need to create a subdirectory called "Administration" and expand it. Then you copy ALL the files inside /Administration/bin to /bin . These files will contain Nop.Admin.dll and other DLLs used by the administrator.

Remember to copy all the plugin dlls to /plugins

+3
source

If you add a link to the Nop.Admin project on Nop.Web, it will be resolved.

+3
source

Just move Nop.Admin.dll to the Nop.web \ bin folder , this error is due to the absence of the Nop.Admin.dll DLL from the material.

+2
source

If you use web deployment through Visual Studio, make sure that you deploy as “RELEASE” in the publication settings, otherwise the administrator directory will be 404. I just thought that I would share it after discovering this in version 3.30 myself ...

+1
source

To publish the NopCommerce app website below is the step:

Step: 1 - publish the Nop.Web project.

Step: 2 - Publish the Nop.Admin project.

Go to the publication folder in which the publication is created

 Here is your answer below (Step :3 is your answer) : 

Step: 3 - Cut off all dlls from Administration and Paste the entire dll folder into bin, which is located in the main bin folder for the entire project.

Step: 4 - Copy two things from the source project and into the App_Data Settings.txt and InstalledPlugins.txt folders that are not published in your publication file, so paste these two files into the publication folder in App_Data. (You need to change the connection string in the Setting.txt file to match your database host).

Step: 5 - Now you need to copy the entire plugins folder from the source folder (but remember this plugins folder, which you need to copy from the Presentation folder not from the main source where the solution file is located.) And replace it with your published plugin.

Step: 6 - Now your publication was ready (now you can deploy to the hosting server)

+1
source

You need to go to the properties of the Nop.Web project and go to the tab "Package / publish on the Internet", and in the "Elements for deployment" section, set it to "All files in this project folder."

You need to do this for each “configuration” that you have in which you are deploying, as it will not set it as the default for any new configurations you may have created.

The reason for this is that the admin project is outside the scope of Nop.Web. Thus, by default, the option "Only files needed to run this application" is only Nop.Web files. If you select "All files in this project folder", it will include the administrator project, because nop.web has links to it.

Hope this helps.

0
source

All Articles