This is also rather urgent to get this resolved. :S

Hey Pat, you can enable deletion of managed package components by logging a case with salesforce support - not everything can be deleted, and you need to be careful about the structure of your package, but you can delete triggers & classes if needed (assuming they are now completely unnecessary). Good overview of deleting managed components here - https://help.salesforce.com/HTViewHelpDoc?id=viewing_deleted_components.htm&language=en_US

Pat,  

Ping me via back channel tomorrow and I will pair up with you and take a look.

Regards,
Irvin

We’ll do. Not sure we have enough time to execute that. Need to the package for show this weekend.

Var you = da man

How about option to uninstall managed package and go from there. 

This is an odd situation. I would do just that, but this is for an app that is already on the AppExchange. It was completely reliant on the visualforce and apex to meet many non-standard requirements.

The owners of the app then discovered Skuid and decided to essentially scrap everything they done, other than the schema, and build with Skuid.

Now the interesting part. They have a trade show they are going to and they want to release the new version for it. The show is next week. So, they are obligated to keep the apex and visualforce as orphans in order in order to not have to do another 6  week security review to submit a new app without any orphans.

Besides, it would be cruel to jettison the orphans so quick.

I did manage to make the necessary updates to the code with the help Irvin.

I really like this line:

“discovered Skuid and decided to essentially scrap everything they done, other than the schema, and build with Skuid.”

Cool…

some good english they’re two "…scrap everything they done… "

Reminds me of a joke.

You know you’re a redneck when you move the fridge and the grass is yellow underneath.