We have a couple of qustions, guys & gals. We’re working on expanding functionality of our 4.1 Nopcommerce application by developing some custom plugins. We’re curious if there are any methods for increasing the speed of plugin development in Visual Studio. We’re currently experiencing the following bottenecks:
• When making changes in plugin views, we have to rebuild the plugin in its entirety to preview a view change (front end development, as an example)
• We cannot use the "edit and continue" feature in Visual Studio to make changes to controllers and other backend files while debugging
We understand we would be able to develop faster if we forked the base Nopcommerce app and developed on it rather than building plugins, but this complicates upgrading to new releases of Nopcommerce, such as 4.2 when available. We would prefer to expand functionality via plugins if possible. Is there a hybrid approach where we can fork the repository and make modifications to the base Nopcommerce app in staging, and roll these changes into a plugin which would be uploadable to production?
Thanks!
Questions regarding increasing the speed/efficienty of plugin development
- 407
- 3708
- 8/4/2013
- India
alldogsoffroad wrote:
• When making changes in plugin views, we have to rebuild the plugin in its entirety to preview a view change (front end development, as an example)
I'm not sure about your other concerns but on particularly for this I'm telling you what I'm doing when you need to modify in plugin views.
1. Modify code in example.cshtml file in visual studio
2. Open root directory /Plugins/YourPlugin/Views/example.cshtml in any editor
3. Copy whole code from example.cshtml(visual studio) to any text editor.
4. Refresh your web page.
This is bit annoying but it spares build time.
Note: This is only for plugin views files changes. If you change in .cs code then you have to build to reflect those changes.
Thank you.
• When making changes in plugin views, we have to rebuild the plugin in its entirety to preview a view change (front end development, as an example)
I'm not sure about your other concerns but on particularly for this I'm telling you what I'm doing when you need to modify in plugin views.
1. Modify code in example.cshtml file in visual studio
2. Open root directory /Plugins/YourPlugin/Views/example.cshtml in any editor
3. Copy whole code from example.cshtml(visual studio) to any text editor.
4. Refresh your web page.
This is bit annoying but it spares build time.
Note: This is only for plugin views files changes. If you change in .cs code then you have to build to reflect those changes.
Thank you.