I'm sure it's an argument of security. Since most know to look in the web.config, they could get access to your database as well. BUT they have to be able to HACK INTO YOUR SERVER first. Like I said, it's an argument. In my 15 years of .net web development, I've heard it all and still prefer to use other means of security as moving the connection string all around is very annoying.
I'm sure it's an argument of security. Since most know to look in the web.config, they could get access to your database as well. BUT they have to be able to HACK INTO YOUR SERVER first. Like I said, it's an argument. In my 15 years of .net web development, I've heard it all and still prefer to use other means of security as moving the connection string all around is very annoying.
LOL... or it might be just as simple as... it was easier for them to write a textfile of the new string (created during setup) then write to the web.config file from code... somehow I think this might be the ticket.... again LOL.
Please look for "dataSettings.json" in Nop.web project.
This is the file where you have to define a connection string. It include { "DataProvider": "", // provider: SqlServer "DataConnectionString": null, // update the null with connection string "RawDataSettings": {} }
anandt is right. In nopCommerce 4.1, you can copy the content from \\Presentation\Nop.Web\App_Data\dataSettings.json and paste it to IIS under e.g. C:\inetpub\wwwroot\[Folder Name]\App_Data\dataSettings.json