How to map nopCommerce 4.0, Nop.Web source code with IIS-7 on local machine with out publish.

Hi

I want to map nopCommerce 4.0 with IIS-7 on local machine with out publish. because previous nopCommerce versions (3.80,3.90) working fine. but nopCommerce 4.0 not working. Please kindly reply how map nopcommerce 4.0 Nop.Web source with IIS-7 on local machine with out publish.

Regards,
K.Amit

Did you check system requirement or iis requirement on nopcommerce official forum?

Could you please look here.

Please try to avoid duplicate post.

we as nopcommerce community should follow standards.

Hope you could understand..!!

Hi sk5202,

I checked system requirement or iis requirement on nopcommerce for nopCommerce 4.0.

For your info i describe below as:

Windows 10
Windows Server above 2008
Internet Information Service (IIS) above 7.0
Install .NET Core
Microsoft .NET Framework 4.6.1
and Using Visual studio 2017.

If you have any solution of my post please suggest me. it's my pleasure.

And I know very well standards of nopcommerce community and flow this.

Because if nop user find any problem then use nopcommerce community forums freely for gathering information by specialist.

Thanks

Not sure what you problem is - do you have an error ?

You should be able to point your IIS server Physical path to your development directory
For example D:\websitedevelopment\Presentation\Nop.Web

In fact if you edit the Nop.Web properties in Visual Studio and adjust the Debug setting App URL to be the same URL Defined in IIS (lets say http://test.mywebsitedevelopment.com)
then VS tells you it will need to set the IIS directory for that domain to your development directory.

That way you can test things like having multiple stores running up different subdmains
i.e. store1.mywebsitedevelopment.com & store2.mywebsitedevelopment.com

I use the above when developing but then when development completed I publish to a local directory so I have a release version which I then send to my website hosting.

One trick for players once ready for production is making sure you dont publish the debug version of web.config to your IIS server directory (or remote server) as the having anything in arguments="" will cause an error.
i.e. change arguments="-argFile IISExeLauncherArgs.txt" to arguments="" in the production version