I'm working to an app service using AutoMapper to mapper entity to Data transfer object and I have this error.
System.MissingMethodException: 'cannot find the method 'AutoMapper.QueryableExtensions.IProjectionExpression AutoMapper.QueryableExtensions.Extensions.Project(System.Linq.IQueryable`1<!!0>)'.'
I don't understand: I have other enitites mappe and they work.
Am I missing something?
In the end I discovered that the problem is the AutoMapper version: the standard template ships with the 3.3.1 version, and if you update to a later version in this case gives and error.
Related
I am trying update my Azure Function App to V4
I have function within it, which is triggered by the IoT Hub.
When I run my App I am getting following error during run time.
Microsoft.Azure.WebJobs.Host: Error indexing method 'iothub_incoming'. Microsoft.Azure.WebJobs.Host: Multiple properties named 'ContentType' found in type 'EventData'.
[2022-12-20T17:13:36.456Z] Error indexing method 'iothub_incoming'
[2022-12-20T17:13:36.456Z] Microsoft.Azure.WebJobs.Host: Error indexing method 'iothub_incoming'. Microsoft.Azure.WebJobs.Host: Multiple properties named 'ContentType' found in type 'EventData'.
Has anyone else experienced this ?
There is a dependency between Azure functions core tools and the V4 Azure function App. A similar issue has been reported on Github in the past. Here is the link to the issue - Microsoft.Azure.WebJobs.Host: Multiple properties named 'ContentType' found in type 'EventData'
The ticket mentions that this issue is fixed with new version of azure function core tools v4.0.4544. You can upgrade the core tolls version using the command below
npm install -g azure-functions-core-tools#4 --unsafe-perm true
Refer the following resource on Changing Core Tools versions
Here the run book to check different compatibilities and any code changes that may need when you Migrate apps from Azure Functions version 3.x to version 4.x
If you still face issues with the function after upgrading the tools, you can report the issue in the GitHub link Azure SDK for .Net issues
Generated a new JHipster application using v5.3.0 with Elasticsearch
I'm using the same JDL that I used with the previous version of JHipster which worked successfully but could not deploy.
I generate successful. No errors. No problems.
When I open the application and try CRUD with my entities...works normally.
For one of my entities, the Elasticsearch search returns a 500 server error.
Again, this is just after generating the application. I haven't changed anything.
This JDL worked in the last version. The failing entity works fine for all CRUD operations...just throws the error when doing a search. All the other entities work fine doing a search.
The JSON response mentions "failed to map to source...to class".
The generator created that mapping without errors. Why would it being failing during a search?
Why do the other entities work OK?
Any ideas? Anybody else have problems?
Bug in JHipster 5.3.0 generator.
See https://github.com/jhipster/generator-jhipster/issues/8222
Guys I know that the azure functions cli has a dependency with RestSharp.dll and I think that is conflicting with one of my Azure Functions.
I am getting a runtime type exception
System.TypeLoadException: 'Could not load type 'RestSharp.IAuthenticator' from assembly 'RestSharp, Version=105.2.3.0, Culture=neutral, PublicKeyToken=null'.'
Now my azure function is dependent on RestSharp nuget Version 104.4.0.0. There is no reference in my project to Version 105.2.3.0. Here is the interesting thing. In my despair I searched my entire computer for the culprit dll version 105.2.3.0 and I found it at AppData\local\Azure.Functions.Cli\1.0.12
Is that it ? Is the Azure functions runtime trying to link with its RestSharp.dll version instead of the dll version of my project ?
Runtime should technically load version 104.4.0.0. However it is still loading the version referred by the runtime (105.2.3.0). I was able to verify this behavior. Have filed a bug for this https://github.com/Azure/azure-functions-host/issues/2832.
In the meantime is it possible to do one of the following:
Update the code to use 105.2.3.0, I see RestSharp.IAuthenticator type is present. It is under a different namespace. There should be another method exposing the same functionality
If the function app is not being used in prod. You could use the beta runtime. You should not encounter this issue in beta runtime (v2.x)
I am following this tutorial (https://atgsupportcentral.motorolasolutions.com/content/emb/docs/manuals/14978403a.pdf), created a simple Windows Forms and successfully can debug it on the scanner (it's a Symbol MC3000).
However I am getting an exception when trying to initialize the CCoreScannerClass:
//Instantiate CoreScanner Class
CCoreScannerClass cCoreScannerClass = new CoreScanner.CCoreScannerClass();
The exact error message is this:
"COM object with CLSID '{9F8D4F16-0F61-4A38-98B3-1F6F80F11C87}' cannot be created due to the following error: 0x80040154."
Can anyone please provide some help? Since it's a COM exception, I assume it's because the class is not registered? Any ideas on how to fix this?
Many thanks.
I got it working by downloading the EMDK for .NET from the Motorola's website:
https://portal.motorolasolutions.com/Support/US-EN/Resolution?solutionId=88177&productDetailGUID=f5563b1ca4151410VgnVCM10000001c7b00aRCRD&detailChannelGUID=a0bde8cea8151410VgnVCM10000001c7b00aRCRD
0x80040154 is an error that, as you mentioned, pertains to the COM class not being registered, which means that COM couldn't find the class factory in the Windows registry. You can use C:\Windows\system32\regsvr32 to register the missing SDK DLL.
I got it working after the installation of the Scanner Management Service
https://portal.motorolasolutions.com/Support/US-EN/Resolution?solutionId=87864&productDetailGUID=f0acd085364cf310VgnVCM10000081c7b10aRCRD&detailChannelGUID=84a76e203763e310VgnVCM1000000389bd0aRCRD
Using Mule IDE version 3.2.3 to invoke JAX-WS web service. In the "Import WSDL" dialogue after entering the WSDL URL and package name the JAX-WS client generation fails with error message
Error generating from WSDL: Thrown by JAXB : A class/interface with same name is already in use. Use a class customization to resolve this conflict.
How do I specify jaxb customization in Mule IDE?
What you are covering with the black colour is key to resolve this issue. Are you sure you are not using a reserved class, or a package name already taken?
Just try with org.example.helloWorld and let us know if it still fails.