cboy wrote:...I could not get my Visual Studio to publish and I can only see the web.admin folder in Visual Studio.
I used Filezilla to put the files from the deploy folder. I did find a Settings.txt file but have not been able to try it yet because I am having an issue with the sub-domain I put it in. Arvixe is working on it.
If you see a Settings.txt, then that is probably cause of your DB error.
(funny, I also had a problem setting up a 2nd sub-domain, that they needed to "reset")
re: "...can only see the web.admin folder in Visual Studio"
I don't know what you mean. In the Solution Explorer?
I used VS to publish to a local folder. But several additional manual steps are required. In VS, first I went to Build/Configuration Manager, and selected Release/Any CPU. Then Build. Then you need to VS publish both the Nop.Web and the Nop.Admin (Admin should be published to an "Administration" subfolder of the folder you published Web to). Then in the published sub folder copy files from the \Administration\bin into the root bin (OK to skip if exists - most will). Additionally I had to manually copy the PlugIns folder. This is where it got ugly. The Deploying.Readme.txt file in \src says
2. Ensure that plugins are copied into \Published\Web\Plugins\ directory
But, it does not say from where!
At the time, I just decided to copy them from the "NoSource" version I'd previously downloaded (root PlugIns folder), because I knew the NoSource version ran OK. You will note that the plugin sub folder names under the NoSource root \PlugIns folder are NOT the same as the folder names in the \src\Plugins folder, the latter being prefixed with "Nop.Plugin.". (Now I see that these non-prefixed folder names are also in ..\src\Presentation\Nop.Web\Plugins, but I'm not sure how they would get there - I think I'd also run the Deploy.bat which fails for me, so maybe from that??? - I'll have to try from scratch to see)
Good luck!