aGorilla wrote:Ok, here's a stupid question...
I'm working on my own application, and it's just a 'web site' app - much smaller/simpler than nop. I'm used to being able to just edit the .cs files, and the change takes instantly.
I realize that with nop, there are libraries, and if I try to change the code in them, I need to update the DLL files in the bin dir.
Does that also apply to the .cs files that are the code behind files for the pages? If so, what DLL are they in?
Thanks, in advance. This one is really driving me crazy.
Yes, you are correct,
In many websites when you make changes to .cs file , there is no need to re-built the project and changes takes place.
But in nopcommerce project, whenever you will make any change in .cs file YOU NEED TO RE-BUILT your project that will update the .dll files/libraries and then only you will be able to see the changes.
In nopCommerce, if you are making change to .aspx page then you don't need to rebuilt/re-compile - It's only .cs file which requires project re-built on any change.
Whenever you make any change in .cs which is inside the nopCommerceStore folder, after you are done with the project re-built, you need to update one dll file which is in bin folder named as "NopCommerceStore.dll". This is the only dll file that is updated when you make any change .cs file (from the nopcommercestore folder).
So the best practice would be : whenever you will make the changes locally in .cs (that is from the nopcommercestore folder), rebuild, then copy the new nopcommercestore.dll file across to the live server. That's it !!!!!
To know more about why on few websites you can make changes in .cs file without re-compiling and why in nopcommerce you are required to re-compile, take a look at this article:
http://www.compiledthoughts.com/2008/05/web-site-vs-web-application-project.html