R
rudolf.ball
Hi Newsgroup,
I have a question about a project I want to realize as a ASP.NET 2.0
Plugin System. I want to have an ASP.NET Base-Application, that handles
Users, Roles, but no content. Then I want to have the ability to write
"plugins". Perfectly, a plugin would mean to me:
- a ASP.NET plugin site with only a <Content> Section, with eg.
textboxes, buttons on it
- a C# Class (DLL), where the logic for the ASP.NET Plugin lies (eg.
The Event for the Button)
I want a plugin to be able to give the user back eg. a PDF file (or
some other file), or an image, text, whatever. The Plugin-Class (DLL)
has to be able to use some Classes I have written for the Base System.
So, in an overview, there I have Base System and a lot of plugins, that
I load at start of the site.
Now the question: How can I do this? Are there any "best practices"?
Tricky? Possible? Or Easy?
Thank you for your help,
Rudi
I have a question about a project I want to realize as a ASP.NET 2.0
Plugin System. I want to have an ASP.NET Base-Application, that handles
Users, Roles, but no content. Then I want to have the ability to write
"plugins". Perfectly, a plugin would mean to me:
- a ASP.NET plugin site with only a <Content> Section, with eg.
textboxes, buttons on it
- a C# Class (DLL), where the logic for the ASP.NET Plugin lies (eg.
The Event for the Button)
I want a plugin to be able to give the user back eg. a PDF file (or
some other file), or an image, text, whatever. The Plugin-Class (DLL)
has to be able to use some Classes I have written for the Base System.
So, in an overview, there I have Base System and a lot of plugins, that
I load at start of the site.
Now the question: How can I do this? Are there any "best practices"?
Tricky? Possible? Or Easy?
Thank you for your help,
Rudi