Apex Code Development You need to sign in to do that
Don't have an account?
JPClark2 Is there any reason to keep unmanged package definitions after a DE ORG has a managed package?
I was hoping to be able to use the unmanaged packages for testing in demo ORGs, but once you convert a packaged to managed, a lot of things don't work as an unmanaged package.
- Custom Links and Buttons need to be modified to prefix the namespace onto any apex pages they are referencing, but nolonger work in an unmanaged package.
- @depricated isn't allowed in any classes for an unmanaged package, but you can't just delete it from your code either. So once a method is in a managed package, there's no way to get rid of it.
- Prefixing the sObjects with the namespace in apex code is perfect fine as long as you don't want to create an unmanaged package.
It seem like these are bugs to me, but when I ask about them, there's some excuse for them. It doesn't make it very easy to maintain an unmanaged package for testing or demos.