Developer Tutorials

Hi Tony,

the ASP.Net Temporary Folders - depending on the System - tend to be either in User Profile
or Systemfolder looking somewhat like this:

%SystemRoot%\Microsoft.Net\Framework\v4.0.30319\Temporary ASP.NET Files\

I tend to watch out that when compiling out of Visual Studio and get some weird behaviour or
when I am making changes to the core - other than adding views to a theme or writing a plugin -

1. IIS Express Webservice from previous compilations is stopped before I compile /clean resources again, for they will be held in Memory and might also falsificate testing
2. Delete all Temp Files/Folders from Temporary Asp.Net Folder
3. Delete obj Folders in Subprojects such as
e.g.
- nop.web obj folder in  -->>{Solution}/Presentation/Nop.Web/obj
same goes for
nop.core, nop.services, nop.data
They will be generated new when you let visual studio create a new compile
4. Delete specific Plugins Folder in nop.web/Plugins Folder if there are some Problems with some of our own plugins


Make sure all "existing" projects you add as references to your plugins like nop.services or whatever - don't copy to your  release folder, if they already exist, for they will exist more than once then in the release and might cause trouble when you have different versions floating around.
Especially if you deploy to your webserver make sure all compiled dll versions exist only once.
IIS tends to pick any assembly after restarting if there are different versions too.

Apfelsine,

When you say the "Delete obj folders", is it OK to delete the whole folder including the obj folder itself?

Yes, I noticed that when I have problems with executing from VS2012, I sometimes have to close my solution and clean everything out, then reopen it and everything is back to normal.

Thanks for your help.

Tony

Hi Tony,

yes, you may just delete the whole obj folder.

greetings
apfelsine