Duplicating Features from SharePoint 2010 and adding them to SharePoint Foundation 2010

Can I copy the kpi feature from SP 2010 to Foundation 2010 and deploy it as a new feature? Theoretically, it would seem possible to just copy the right folder(s) from Features, or Solutions or Templates, if needed, and install them on Foundation. Maybe I might have to change the guids, although I don't think I would even need to do that as long as it will never be on the same box as it's originator is. So what would prevent this from working? Seems to me, when you get a more expensive version, that all Microsoft does is to add more features programatically but these are added in the same way anybody adds a feature of their own.

Thanks.
LVL 9
BobHavertyComhAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rainer JeschorCommented:
Hi,
from my experience:
There are two installers:
- Foundation
- Server
The license of the SharePoint server can be changed in Central admin, therefore the installer must include everything you need - it is just a matter of what features you see in the UI/Powershell...

Second I think that just copying the feature folders will not be enough. There are custom DLLs deployed very deep into the GAC, precompiled and also a lot of COM references and add-ins.
Therefore it is not possible to debug SharePoint code on your local machine by just copying the DLLs and references.

And the third aspect is the regulatory side:
Even if it would just be a paper license, you would simply violate the license agreements.

HTH
Rainer
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BobHavertyComhAuthor Commented:
Yes, I understand the regulatory side, this is more of a theoretical question to learn how this stuff works. I'm not actually going to do this because I would have to completely remove it if there was an upgrade or else all hell would break loose.

If, for example, the KPI feature was added the same way any developer adds a feature of his own, why would the GAC, COM references etc.....be a factor? If I deploy a custom feature, if there are any issues with GAC, COM, it seems as though the installation takes care of all of that for me.

So why would my new feature be able to be added without me knowing the GAC and COM aspects, but KPI has to use or reference the GAC and COM in some way that a regular feature installation performed by me will not take care of?

Essentially, besides having an upgrade installation do it for you, what is the difference between the deployment of a KPI during an upgrade from Foundation to SP and the deployment of a custom feature to Foundation, copied from KPI, that does the same thing? Does it have something to do with whether the KPI is a core feature and therefore has some special locks and requirements that new custom features that I add don't have? Could these be found and removed or edited in the xml files?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.