Effective plugin development (abount build time)

I am developing a plugin and rebuild almost whole solution after every code changes. (Stop debugging. Clean and rebuild plugin and web project. Debug project again.) It takes time and increase development time. How can I follow path for more effective plugin development in Nop?

You do not need to build the whole solution every time. Rather you need to build the specific plugin which one you are developing. Build the plugin must needed when you change the .cs file but for .cshmtl, .css and .js you can directly change it from the output(Presentation==>Nop.Web==>Plugins) folder it will decrease the development time. But remember at the end you need to take the changes to the main plugin related files otherwise you will lose the changes when build the plugin as at every builds the nopcommerce engine replace the output folder contents with the latest change of the specific plugin project.

sina.islam wrote:
Yes you are right but another problem about I need to restart debug session of Web project otherwise plugin changes does not reloaded in Web project. Can I do changes in plugin and see changes running web project without restart? (Currently I need to restart project every time.)