Could not transform licenses file into a binary resource - Error on Solution Build

Sofar, In visual studio, I got get the Customisation Project to build successfully, but the project still won’t publish. Even a fresh installation does this. 

I have same error since 22R2(23R1) when doing debug for customization projects. never had this issue before. so I copy the code back to Acumatica customization screen to publish.

Incase it helps someone else.

I just hit this trying to build website for my customization project in Visual Studio into Acumatica 23R1.

Eventually I followed the overkill advice, and just deleted licenses.lcix completely from my installation folder, this allowed VS to finish building.

In case it was not clear from my other post, I believe the issue comes when trying to build the whole site. In Property Pages, you can turn off building the site, which is recommended by Acumatica. Still, it's pretty easy to do, and that's what causes the issue. Fix is to only build the project, or if you've already tried to build the whole site, repair the install by 'upgrading' to the same version.

Hello. Can you step through the solution explaining it like I am 5 yrs old? I have just installed a completely fresh database and web Acumatica. Created a new customisation project, specified a particular page to modify and saved it. Publish does not work due to the error as noted in this case.

So what is the workaround to the bug? 

» I did an installation refresh by running just a web upgrade on the same version of the installer

Ok, this makes sense, can do this,

» building ONLY the library again

What library? Where is it?

» ... Property Pages, you can turn off building the site, which is recommended by Acumatica.

Which Project/solution is this done in? Can you provide a screenshot of what you are changing from/to?

And could you provide a reference to the Acumatica recommendation?

» Still, it's pretty easy to do, and that's what causes the issue.

Does this mean changing the Property Pages (somewhere) will be a permanent fix and we can publish from the standard interface now?

@MarkOM - By your description, you haven't compiled anything, so it seems like you may be receiving this error for a different reason. The fix may still be to upgrade in place. It does not require compiling. Just that if you are going to compile an extension library, make sure not to 'build' the site in Visual Studio.

Hi I tried the approach given above but it still does not work. Are there any other approaches to this?

You tried an in-place upgrade?

Have you tried deleting licenses.lcix directly?

It sounds to me like you’re trying to build the whole site, not just the one folder.  
I’m not good enough with Visual Studio to guide you around that, but deleting licenses.lcix got me past this (because my computer was no longer trying to verify versions for irrelevant to me dlls)

@Acu Support - 
Would be helpful to have an “explain like I’m 5” series of steps for how to not build the entire site when using Visual Studio, quite common for people to be playing outside their area when they first try to develop a customization.  (Like me, I’m playing outside my direct skill area.)

Hi @darylbowman @WillHowardOpenUni I tried deleting the license file as well as doing a website upgrade but face the same issue. I am currently only rebuilding my customization code which is already working as expected. 

Any other workarounds available?

Thank you!

Here are the steps to prevent building the attached website. This should be done before building your solution for the first time. If you’ve already accidentally built the site, you’ll need to reinstall Acumatica or perform an in-place upgrade first. When that’s finished, confirm it’s not set to build and try building your solution again, by:

1. Right-click the attached website in VS and select ‘Property Pages’:

   

2. In the ‘Property Pages’ dialog, select the ‘Build’ section:

   

    

3. Change ‘Before running startup page:’ from ‘Build Web Site’ to ‘No Build’
4. Uncheck ‘Build Web site as part of solution’
5. Click ‘OK’ to close the dialog