My application has 3 sharepoint parts:
- a Administration page to configure the application
- a timer job and
- a webpart to view data from the application
I built them all into the same feature. When I run the solution from VS 2010, it takes me to the Server settings page and everything works fine. I can access both the admin page and add the webpart to a page.
If I switch to the regular sharepoint page, I can see my webpart listed, but I can't add it to the page. I get an error saying it can't find it or something.
I'm guessing that's because I set the scope of my feature to be Site instead of farm.
So...here's the question. What is the best way to architect this?
I would like to webpart to be available to all the pages in the WebApplication since my product is deals with the web application.
Just mark my feature as Farm wide?
Pull the webpart out of the feature into it's own project?
I want to keep it easy to deploy if possible.