This name is cooler than the deep adventure.
Dynamics axapta mounts B/S to the SharePoint framework, which is another highlight of Ms. ArticleTry to analyze the solution of dynamics axapta's B/s from the principle to implementation.
Since it is deployed on SharePoint, you need to have a rough understanding of SharePoint first. the two articles on msdn introduced the basic principles of SharePoint and the principles of webpart. After reading these articles, I felt that I didn't have to bother myself.
Basic Principles of SharePoint
Http://msdn.microsoft.com/msdnmag/issues/04/07/WindowsSharePointServices/
This article introduces the similarities and differences between the two SharePoint products WSS and SPS, the difference between WSS and its predecessors STS, the architecture of WSS, the principle of WSS receiving requests, and the concept of virtual server, the concept of site set, including path and exclusion path. technically, the difference between SharePoint and common websites is that all site data in Sharepoint is stored in the content database, while common site data is stored on a disk in the form of files.
Principles of webpart and creation of webpart
Http://msdn.microsoft.com/msdnmag/issues/04/08/WebParts/
This article mainly introduces the principles and production of webpart. webpart is essentially a custom control in Asp.net. To put it bluntly, it is the process of splicing HTML and JavaScript on the server side, it is the most important to have a solid knowledge of HTML and Javascript. You can see which method to reload to render HTML.
After referencing others' articles, the first part of the task is much simpler.