Refer toCodeOrganization method to adjust the Organization Mode of custom Ajax controls in pqsys. Although there is only one control, it will inevitably increase in the future and there will be only one unified rule, to facilitate code addition and maintenance in the future;
A new problem occurred while adjusting the structure. The expected results are similar to the organizational structure of controls in the ajaxcontroltoolkit. It is hoped that a project can contain multiple Ajax extender controls. For example, now I have created an Asp.net Ajax control project named customajaxcontrols, which will automatically generate three files. Delete these three files, and then add a new Asp.net Ajax extender control named hoverbutton. Then, compile the project without doing anything. And use this control in a test page. The following error is returned:
[Invalidoperationexception: assemb' mamajaxcontrol, version = 0.0.0.0, culture = neutral, publickeytoken = NULL 'ins ins a web resource with name' customajaxcontrol. hoverbuttonbehavior. js', but does not contain an embedded resource with name' mamajaxcontrol. hoverbuttonbehavior. js'.]
The general meaning is that the compiled control DLL does not have the JS resource file required.
After one morning's search, I found the crux of the problem. For the JS files of all newly added controls, set the build action attribute of the file to embeded resource.
That's simple.