By using this website, you agree to our Terms of Use (click here)
I know there is a postman process for this, but if I destroy a custom's extension library from TRUE rookie visual studio move - is there any file based methods for clearing out the customs to unpublish them on a site restart? (working through the T's series courses)
Is the UNPUBLISH ALL button on the Customization Projects (SM204505) screen broken for you?
Or are you looking for it to unpublish automatically on a site restart?
A cautionary tail...
I feel that and, regrettably, don't have a solution for you but I can certainly confirm that things get messy over time. We've had two different customization projects leave behind screens, tables, and custom fields within our system that, years later and several updates later, are still there. I'm not sure who's responsibility it is to "clean things up" when UNPUBLISH ALL is initiated, be it Acumatica themselves or the Customization Project publisher, but I know that not everything gets unpublished the way I think it should be when it is... This can cause things to get quite confusing when integrating other apps and has forced us to be very, VERY, careful about the what we choose to publish and test.
I had published the wrong .dll in the wrong spot. I believe I just spun up a new test site. A simple change to the publishing directory for the project was the real magic.