I have an issue with importing solution. First of all i will explain my method of importing.
In our organisation we have all the solutions in source control (Extracted by solution packager as Both - Managed and Unmanaged). thanks to that we can build Managed or UnManaged Package from those files.
I have three solutions: Solution_1, Solution_2 and Solution_3. Solution_3 is dependent from 1 and 2. We decided to merge solution 1 and 2 in one solution, lets say Solution_12. Now is the problem:
When i am importing Solution_12 and Solution_3 as Managed, all works fine. When i am importing Solution_12 as Managed and Solution_3 as unmanaged, also all is fine. The probe occurs when I am importing Solution_12 as unmanaged and Solution_3 as Managed. In this situation Solution_3 cannot be imported:
The import of the solution Solution_3 failed. The following components are missing in your system and are not included in the solution. Import the managed solutions that contain these components (Solution_12 (1.0.0.5)) and then try importing this solution again.
Required components are existing in organisation in Solution_12 but when importing they are unavaiable somehow.
Anybody have an idea what could be wrong?
I found out a solution. The key was that any Managed solution cannot be dependant from Unmanaged solution.
Related
When I import androidx.activity.result.ActivityResult; my IDE says: can not resolve symbol 'result' as bellow:
.
In different similar situations, e.g., cannot access androidx activity result activityresultcaller and package androidx activity result does not exist, I see that the problem is solved by upgrading androidx.activity, androidx.appcompat, and androidx.fragment in the dependency part of the build.gradle.
I tried to upgrade different combination of the above packages in the module build.gradle, but non of them solved the problem.
Does anyone know how I can solve it? Thanks.
I am trying to use Microsoft´s WorldLockingTools (repo see here) in my Unity Mixed Reality project. Therefore I need to add the Frozen World Engine DLL to my Unity Project. In Microsoft´s Documentation they describe to do this via nuget. I want to add the dependencies manually like described in this thread, since for me it´s not possible to use nuget (I have no network-access on that computer). I was able to extract the .dll, but if I add it to my project as described in that thread, unity still can´t find the dll. Do I need to do some further steps than just adding the dll to my Asset-Folder? If yes, can you please tell me which steps they are? I would be really thankful for that!
Best regards!
OK I figured out the reason behind this misbehavior. The problem is, that there is a c#-Script within the nuget-package additional to the dlls which has to be placed within the WorldLocking.Engine folder. After that all Exceptions disappeared and it seems to work now! I Hope I could help anybody who comes across this Question.
I may have done something wrong because since the v9 I can't get resharper to suggest classes from different namespaces (different from the current one) if I don't type the using first.
But anything outside the project is ok. So it looks in imported dlls without any problem but won't look in the current project.
Any idea how I could have done that? (looked at the jetbrains forum and didn't see any similar issue so I assume it's not a bug)
Thank you
I develop with Visual Studio. I have a class library that contains code common to many products I develop, and is now in use by 15+ solutions. I do LOB apps for my non-software company.
I've been adding this class library project directly to the solutions of all the solutions that need to use it. But I've been using NuGet to pull in many 3rd party packages and I really like its way of doings things. I'm thinking about adding this utility library as a NuGet package in our own repository rather than adding it directly as a project reference in the solution.
Is this a good idea? What criteria should I use to determine when to use NuGet vs when not to for internal class libraries? I realize that some might think this is an opinion based question, but I'm looking for specifically what criteria you'd use to decide rather than opinions about which is better.
Internal libraries that used and worked on by multiple teams can be exposed as Nuget packages. This way, multiple teams can work on the library, and each of them can update to a version as and when needed by that particular team.
Is there any tool / automatism to import an XPO, exported from AX 2009 to AX 4.0?
The straight way does not work, since properties listed in XPO differ, e.g. I get the exception that import has been cancelled because of "...PROPERTY found, DATASOURCE expected..."
Only information I found is the one linked
Any tipps are appreciated!
#edit:
After testing and trying - import partitially works.
What I'm missing are:
indices on tables
fieldGroups on tables
deleteActions on tables
relations on tables
You can't out of the box "downgrade" projects. You can migrate code to the next version but you can't go backwards.
With that said, if you can import some kinds of objects is by accident, but it is not a supported feature. But you can export objects one by one (or type by type) and then try to import the ones that don't fail and replicate manually the ones that throw errors.
Another "solution" is try to modify the XPO manually based on the received errors during the previous step, but this is totally undocumented and will be doomed to try-and-error.