I have a current project task where I am supposed to add a button (and additional functionality) to a dotnetpanel page. I just wanted to verify if the following processes are the only available paths to making changes to dotnetpanel...
- Make changes to the source and recompile, then copy the new files over the old ones
- Have other web applications communicate with dotnetpanel using the API
- Create add-on
Regarding the first option, if I choose this option it implies I can have added functionality exactly where I want it in dotnetpanel. Problem is that if a new version of dotnetpanel comes up then I will have to re-apply my changes to the new sources and recompile. I don't like this because I beileve one should only have to make changes if there is a bug or something is broken but it seems like this may still be my bast option because of the functionality it affords me.
With the second option, this is really for people that already have a seperate website or application and they want to add some dotnetpanel functionality to the application.
The third method doesn't give you the same level of integration as the first but I believe its strong point is that once you develop an add-on, you do not necessarily have to worry about dotnetpanel core version changes.
Assuming what I have said above is correct, what does the dotnetpanel group suggest to developers regarding creating additional functionality for dotnetpanel?
Going back to the first option, are there any tutorials available?
Again feel free to correct me where my thinking is not right, I just want to make sure I understand some of the concepts.