Acumatica unable to publish the Customization Package - acumatica

I am trying to publish the customization package on Acumatica Version 17.204.0019.
But I am getting the following error :
Validating Binary Files
Aspose.Words.dll Method signature was changed: System.Void   [0...,0...]::.ctor(System.Int32,System.Int32) declared in Aspose.Words.dll
Aspose.Words.dll Failed to resolve method reference: System.Void   [0...,0...]::Set(System.Int32,System.Int32,  ) declared in Aspose.Words.dll
Aspose.Words.dll Failed to resolve method reference:      [0...,0...]::Get(System.Int32,System.Int32) declared in Aspose.Words.dll
Aspose.Words.dll Failed to resolve method reference:    /&    /[0...,0...]::Address(System.Int32,System.Int32) declared in Aspose.Words.dll
Aspose.Words.dll Method signature was changed: System.Void    /[0...,0...]::.ctor(System.Int32,System.Int32) declared in Aspose.Words.dll
We have installed Aspose.Words via Nuget Package Manager and we want to include it in package. But as you see Acumatica is trying to validate Aspose.Words.dll bynary files.
How can we disable to validate binary files while publishing the customization package? Or how to solve problem? In package we have correctly included every dll(Copy Local property is set to true on aspose dll).

To be honest, it's too soon to confidently say, whether this behavior is caused by a potential issue with Acumatica binary file validation or something else. All details had been forwarded to Acumatica Engeeniring Team for further investigation. Will post an update here as soon as I hear back from engineering.
Based upon the response from engineering, to get over this issue you should proceed as follows:
Create a cstValidationIgnore.txt text file in your local Acumatica ERP website's App_Data folder
Copy all 5 error messages generated for Aspose.Words.dll from the Compilation dialog and paste them into the cstValidationIgnore.txt text file created on step 1 (during the Binary Validation stage errors listed in the cstValidationIgnore.txt text file will be ignored)
Open the Customization Manager and include cstValidationIgnore.txt text file into the customization project, that already contains Aspose.Words.dll
Republish the customization

Related

Error: Cannot add the specified assembly to the global assembly cache:Select.Pdf.dll

I add licensed select.pdf.dll to my SharePoint project. This dll file has added in both the visual studio reference and the package section(Deploy target as 'Global Assembly Cache (GAC)').
I was not able to deploy my solution to my sharepoint development server, with the error message
“Error occurred in deployment step 'Add Solution': Error: Cannot add the specified assembly to the global assembly cache: Select.Pdf.dll.”
I have googled the problem, someone cannot deploy because the .dll they want to deploy already existed in %windir%\assembly folder and the .dll is locked by other process.
VS2015 build error: Cannot add the specified assembly to the global assembly cache
https://devramblings.wordpress.com/2011/03/23/error-cannot-add-the-specified-assembly-to-the-global-assembly-cache/
However, the "Select.Pdf.dll" I want to deploy has never been deployed before, the %windir%\assembly and %windir%\Microsoft.Net\assembly folders do not have same name dll. file in them.
I have tried to restart VS, and reset IIS. the problem still existed.
Is there any way to solve the problem? Thank you.
You need to add the relevant .dep files also. When you add your assembly to the advanced section of the package you can add Class Resources at the bottom of the dialog. In my case I had to add Select.Tools.dep and Select.Html.dep before I could deploy my sharepoint solution.
#Mundi's answer works, only clarification is that for us, only selecting Select.Html.dep was enough. It is to be noted that you have to specify that you want to view all files (not just .dll) when selecting the additional Class Resources.
Alternative solution that worked for development scenario (but not advisable for production) is using appropriate gacutil.exe to your .net version.

WCF ServiceClient Code Generation fails when types in Catel.Core dll are reused (including small example project)

today I created a new Project, using Catel Framework in Silverlight.
However - I am facing a Problem when generating the service-Client for the WCF-Service in the silverlight Project.
To reproduce the issue:
- open solution,
build
"Show all files" in the Silverlight Project (CatelWCF.Problem)
Observe:
beneath node "WCFService" in Reference.cs - all Code generated successfully
now "configure service-reference" (right click "WCFService", Configure)
choose radio-button Option "Reuse types in all referenced assemblies", followed by OK (before it was configured to use all but Catel.Core)
Observe:
error-message in Error-List
view file "Reference.cs" - it is empty.
In WPF there is no Problem whatsoever, even if all assemblies are referenced. (CatelWCF.Problem.WPFClient Project)
Any ideas?
Johannes Colmsee
Update:
Sorry, the demo-Project can be downloaded here:
Demo
Update2: About why "observe" #1 Shows a succesfully generated file: "Catel.Core.dll" is explicitly excluded from referenced assemblies when you open the Project.
I narrowed down the Problem to one specific type in Catel.Core dll - Geert, please check what is wrong with this class:
Catel.Runtime.Serialization.Xml.XmlSerializationContextInfo
Regards
Johannes Colmsee
Update: Creating a sample Project with a (almost exact) copy of that class - no Problems.

Video Ads of Vungle SDK

I had follow the instruction from the channel 9
https://channel9.msdn.com/Blogs/Seth-Juarez/How-To-Integrate-the-Vungle-SDK-for-Windows-10?ocid=player
and I get the error below:
General metadata correctness
Error Found: The general metadata correctness test detected the following errors:
The assembly VungleSDK in file VungleSDK.winmd has a non-empty manifest resources table. Every Windows Runtime assembly must have an empty manifest resources table.
Impact if not fixed: Windows store doesn't allow apps that don't pass Windows Runtime Metadata Validation.
How to fix: Please ensure that the compiler you are using to generate your Windows Runtime types is up to date with the Windows Runtime specifications.
I does not understand this errors, anyone can help?
I had an error look like the same as the problem with the sdk, but not with the SDK, its in my own project.
The project doesen't contains anything except the project.json and refers a SharedProject which contains only one .cs file.
I get the same error, but I can't find the sollution.
I tryed:
- Add app.manifest (from template)
- Resource Dictionary
- Resource File
Both was empty as the error sais "Windows Runtime assembly must have an empty manifest resources table", so I created some empty one.
I would be happy to know what did you do with the Vungle SDK, what caused the problem and what solved it.
The Vungle winmd file contains same files like my projects winmd...
Here is the answer for my own problem.
Finally I found what caused the problem, by inspecting the .text file in winmd file and locate the file whose content was included in the .text.
Under the winmd project Properties the template generates a .rd.xml ( usually your package name) which is a resource dictionary what sould be removed in my case.
I know it won't help to solve the prolem with the old SDK which were patched earlyer, but if somebody get the error message on package validation and don't know what to do, here is something he can try.
(Just to be clear my problem not connected to the SDK I just get the same error message on validation)

Could not load file or assembly My.Custom.Assembly.dll, Version=1.0.0.0 Culture=neutral, PublicKeyToken=def751c98b41d765 or one of its dependencies

In Microsoft Dynamics CRM 2011, I wrote one plug-in in C# for Account entity to do some operations on fields when Account record is created. In C# code I created my own custom assembly called My.Custom.Assembly.dll. Which contains some generic methods those I can use often in my plug-in. And I using this My.Custom.Assembly.dll and also added in reference in my project. Project builds successfully and plug-in registration also. The problem I faced when I was creating a Account record. Its throwing an error: "Could not load file or assembly My.Custom.Assembly.dll, Version=1.0.0.0 Culture=neutral, PublicKeyToken=def751c98b41d765 or one of its dependencies.The System cannot find the file specified." I got to know the problem is with My.Custom.Assembly.dll. Can you please help me to solve this problem..?
Your custom assembly cannot be loaded during the execution of your plugin.
Either install it in the GAC or merge it with your plugin assembly.
See my answer at Plugin with references not working on CRM 2011
A good place to start debugging this type of issue is to use Fusion Log Viewer to see the details of how .Net runtime is attempting to load the assembly. http://msdn.microsoft.com/en-us/library/e74a18c4(v=VS.100).aspx
Based on what you find in the log post more details if you need additional assitance.
You may also want to read up on How .net loads Assemblies

webpart - sharepoints

I've created a user control and added that user control to my webpart. But when i try to add the webpart in a page. i am facing the above stated problem.I ensured that dll was present in GAC.
I've created a user control and added that user control to my class library. I've compiled and signed the dll and have added it to the gac. But when i try to add the webpart in a page i'm getting the below mentioned error.And made necessary changes in web.config file.
I've made sure that dll is there in the gac. But i'm still getting the same error.
" An error occurred during the processing of . Could not load the assembly 'Generate , Version=1.0.0.0, Culture=neutral, PublicKeyToken=e5b42758c1bfd2df'. Make sure that it is compiled before accessing the page. "
please help me.
Make sure the user control inherits
from the solution assembly in the Control tag
Load the control in the CreateChildControls method of the Web Part
Put this user control under the CONTROLTEMPLATES folder
Are you deploying is as a Feature?
To debug locally, check the following in your config file:
* customErrors=off
* Enable Stack Traces by adding CallStack=”true” to the SafeMode tag
* Set the compilation debug attribute to "true"

Resources