Something that I've found that I've had to do to get the platform working on IIS is run the web platform installer for nopcommerce and install a default site in IIS, I don't know why, but whenever I manually create a virtual directory in IIS, manually configure it, set ASP.NET to the correct version, and copy over the standard non-source files to inetpub it just doesn't seem to work!
After running the web platform installer I then copy over my changed files to the directory that gets created in C:\inetpub\wwwroot\mywebsite\ and ensure my connectionstrings.config file is pointing to the correct database with correct login details etc.
What OS and IIS version are your running? In Win7 and IIs 6.1 add an application under "Default Web Site" Set the physical path to the nopcommercestore folder Set the application pool to ASP.NET 4.0 Add default.aspx under default document Then http://localhost/alias should default to the default document.
Under XP (can't remember the version of IIS) add as a virtual directory under Defualt Web Site. I always test changes with IIS unless i am debugging.
Yes, the NopCommerceStore folder needs to be an application. Looking at the second pic, the root of your site/application should be the nopcommercestore folder. You are one level too high. This nopcommercestore folder is all you need to copy to the production server when your app is ready. The other source folders are there if you need to make changes and recompile. They compile into dll's that are moved to the nopcommerstore\bin folder. If you have not done so you will need to allow the network service "modify" access to the images\thumbs folder and the administration\backup folder.
>> They compile into dll's that are moved to the nopcommerstore\bin folder.
The Bin folder is white, as in it need to be "added to the project" ??
>> Looking at the second pic, the root of your site/application should be the nopcommercestore folder.
I moved all the files to the C:\inetpub\wwwroot folder. If I just moved the Nopcommerstore folder over, what do I do with the rest of those folders? Those folders are also at the "top" level.
There is an option (r-click NopCommerceStore) to "Convert to Web Application" in Visual Studio. If I did that, would that just add the NopCommerceStore folder to IIS? (I have since deleted the last installation and the wwwroot file has no NOP in it now).
The Bin folder is white, as in it need to be "added to the project" ??
No need to do anything with the bin folder. That is where your compiled dll's get updated. Just leave as is.
CliveLoftyAnstruther wrote:
I moved all the files to the C:\inetpub\wwwroot folder. If I just moved the Nopcommerstore folder over, what do I do with the rest of those folders? Those folders are also at the "top" level.
You do not necessarily need to move any of the files. Just point the IIS application to the nopcommercestore folder. When you unpack the project you get the folders that contain the source code for the DLL's and the NopCommerceStore folder along with the solution file for visual studio. Just leave as is and go to IIS and right-click "Default Web Site" and select the "Add application" selection. Then you put in the physical path to the NopCommerceStore folder whereever you unpacked it. Give it an alias name which is the name of the site and select the application pool as 4.0.
CliveLoftyAnstruther wrote:
There is an option (r-click NopCommerceStore) to "Convert to Web Application" in Visual Studio. If I did that, would that just add the NopCommerceStore folder to IIS? (I have since deleted the last installation and the wwwroot file has no NOP in it now).
You should not need to to this in Visual Studio. Just set it up in IIS as above. It is already defined as a web application and that is why in IIS you set it up as an application. Hope this helps...jeff