We have a custom packages created by some team from our company and it was working in 2021 version but now we have windows 11 machine and 2024.10 version of UiPath.Since then we couldnt install the packages as its saying its not compatibles.So the other team worked on it and they have pushed the latest pacakges we are ale to install them but getting error during compilation. attaching the pictures for reference.
Thanks for responding. I donât have UiPath.Emgucv.bundle in my dependencies.And also can you let me know how to check the studio and .net versions are up to date?
The person who developed the custom packages used .net 6 version and UiPath 2024.10 is targeting .net 4.6.1 !! Could that be an issue?
Iâm pretty sure the guy above just threw your issue into a GPT and parrotted the reply as its not accurate at all.
Your issue si for sure .NET compatibility.
They developer made they code compatible with âWindows - legacyâ projects, which are 32bit and have been phased out. âWindowsâ and âCross Platformâ projects are 64 bit and require .NET 6.0 or higher (I think thats the min).
Studio itself I think is on .NET 7.0 or 8.0 by now.
You need to get the original dev to update their code.
Thank you.How to check the .net version using by UiPath. I have checked few articles and they mentioned to check in registry editor App and there it was showing like 4.8.1 or Higher .net version.
If .net version is the issue can we upgrade the .net version to make it compatible with the Custom packages. As i was getting conflict messages when i tried to install the custom packages at first
@Jon_Smith Yes! they did developed which were compatible for windows legacy but now they worked on it and gave us the new version that is getting issues when we install and compiling the BOT.Is there any fix that we could from UiPath Side or the other person should work on his side? Please help me on this
The new version looks like it only works in Windows Legacy, you can confirm with them. Ask if its 32 bit or 64 bit and want .NET framework version its made on, if its 32 bit its not compatible.
@Jon_Smith Actually we have checked whether the new package is working fir Windows legacy Projects but unfortunately its not working for them. We were getting compatible issues and its working in Windows projects however getting issues after installation.As you suggested will check with him if he used 32 or 64 bit
Before warning me, please be respectful yourself. As I mentioned in my previous response, I tried to solve the issue by conducting research and using my own technical knowledge. Using GPT or researching on .NET forums are also valid problem-solving techniques. The word âparrottedâ in the sentence you wrote is disrespectful