sure you need the settings file, and you need also to connect to the database on the new host., and last but not least you must migrate the database-content from local to host. when all this is done your server presents the same content.
I've noticed that if I deploy via Web Deploy or File System Visual Studio does not create the App_Data/Settings.txt file. This causes the install page to run when launched.
So, I tried to add the settings.text file from the source code into the WWWRoot folder before deploying and the site throws an error "We're sorry, an internal error occurred."
I'm stumped as to what I can do!
Do I just deploy the files again and accept that i'll have to go through the install again? Or is there something in VS that I can do to resolve this?
Well I've figured out how to stop the need for a 2nd installation when deploying via WebDeploy so I'll add it here for closure just in case anyone else has the same issues I had.
- Publish via Web Deploy - When it tries loading the page when the ublish is complete, close the browser window asap - Use FTP to add the Settings.txt and the InstalledPlugins.txt files from the Presentation/Nop.Web/App_Data folder in your source code into the App_Data folder in your web directory. - Run the website
The above steps allowed me to load Nop just as it has been running on my local machine.
Please note, I originally installed nop on my local machine pointing directly at the remote database. If you use a local db you will need to change the settings.txt connection properties before uploading.
You can use the publish from visual studion if you do the following Include you InstalledPlugins.txt & Settings.txt in to the project in the App_Data folder Make sure the files are showing as content
Then unload the Nop.Web Project, and open project file in in Edit mode Look for ExcludeRootBinariesDeployment section
And you will find App_Data\Settings.txt and App_Data\InstalledPlugins.txt are files that are being excluded from deployment.
If you delete these two lines Then load project and try publish. Then you should not need to copy it using FTP
This is what you would be looking for in project <Target Name="ExcludeRootBinariesDeployment"> <ExcludeFilesFromDeployment> .... App_Data\Settings.txt; App_Data\InstalledPlugins; .... </ExcludeFilesFromDeployment> </Target>
If the setting.txt file is deployed with the webdeploy you wont get the install page when you open site Just make sure you have you setting and plugin files correct
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.