I am trying to upgrade my code from using Crystal Reports 11 to Crystal Reports 13, but I am having troubles since I can't find the craxdrt.dll on the new Crystal Reports 13 package.
I used to import craxdrt.dll then instantiate it as a COM component
#import "craxdrt.dll"
IApplicationPtr m_pCrystalEngine;
m_pCrystalEngine.CreateInstance("CrystalRuntime.Application.11");
Any idea how can I upgrade my code ?!!
The RDC was deprecated in CR9 and stopped shipping as of CR XI R2 (11.5), which itself is out of support already.
A walkaround is to write a COM or C++/CLI interop layer based on the .Net version of Crystal Report.
Related
I'm trying to build a simple object detection runner, really just following this MS Docs guide: https://learn.microsoft.com/en-us/windows/ai/windows-ml/tutorials/tensorflow-deploy-model
I already figured out building the View and adding capabilities so the provided code actually compiles.
Just one more problem right now: When creating the session, it crashes claiming "Unknown model file format version" which seems to translate to "Opset of the model you use is not supported".
Looking at github issues google showed me, I'm supposed to install the Microsoft.AI.MachineLearning nuget package and all is well. Except when I installed it, nothing changed.
So, what's left to do beside open yet another github issue? I already re-exported my model from opset 15 to opset 11 because the nuget package only supports that.
I'm on windows 10, UWP targeting 2004.
After upgrading to iOS13 beta 6 using Xcode 11 beta 5 I receive this message when running on an iPhone SE device.
dyld: Symbol not found: _$s7SwiftUI7BindingVyxGAA0C11ConvertibleAAMc
Referenced from: /var/containers/Bundle/Application/3B128240-B05E-4C1C-A0E1-55D22683B49E/BleAdvApp.app/BleAdvApp
Expected in: /System/Library/Frameworks/SwiftUI.framework/SwiftUI
in /var/containers/Bundle/Application/3B128240-B05E-4C1C-A0E1-55D22683B49E/BleAdvApp.app/BleAdvApp
Using the simulator there's no such message, and it has been ok with iOS13 beta 5 on the device, tool
Compiling is fine, the message is shown at startup of the application on the iPhone with an
Thread 1: signal SIGABRT
Since there is no Xcode 11 beta 6, the Xcode is still running on beta 5 on MacOS Mojave 10.14.5 (18F132).
I created a simple SwiftUI example from scratch, that's working without any issue on the actual phone and the simulator.
What me also wonders is that there's no path /var/containers on my Mac at all?
Any idea on how to proceed?
With the update to Xcode 11 beta 6 and using iOS 13 beta 7 the issue does not appear anymore. I used the code posted in the links above.
SwiftUI APIs deprecated in previous betas are now removed. (52587863)
Several extensions to the Binding structure are removed. (51624798)
The Binding structure’s conditional conformance to the Collection protocol is removed. (51624798)
I believe the answer is this section of release notes. Binding’s removal from conforming to collection.
In a new project utilizing CoreData, crash does not occur. Any other project with dynamic data that is not CoreData, like a set or array crashes with this error.
I followed the migration guide from the notes to account for this removal, but crash still occurs on device. Simulator, previews, etc are all fine.
I am trying to use the CardBuilder.showStackIndicator(boolean) method, which was introduced in version XE22, but Android Studio tells me that the method can not be found.
I have the latest version installed from the SDK Manager and the latest software version installed on my Glass device. Is there something else that needs to be done to use this method?
This method should be in revision 11 of the GDK: make sure you've updated your add-on and refreshed your IDE.
If it doesn't show up in your IDE, try compiling anyway to make sure it's not a sync issue between autocomplete/autocompile and your SDK.
upgraded Jubula from 1.2 to 2.0 (latest), switched jar-file and run a clean. AUT is a RCP-Application, wich is installed via Java Web Start (Jubula executes a Batch-file).
After the upgrade Jubula starts the AUT -but when workbench is loaded Jubula does not recognize it and the progress "starting aut" continuous.
Thanks for any tips / hints
There are a couple of things to try when you can no longer test an RCP AUT after an upgrade:
Ensure the old org.eclipse.jubula.rc.rcp_[version].jar in your AUT's plugins directory is replaced with the new version from [jubula_install_directory]/development/rcp-support.zip
Ensure your AUT's configuration/config.ini file still references the Jubula remote control plugin: osgi.bundles=[your AUT's bundles],org.eclipse.jubula.rc.rcp#start
More information and more Q&A about this issue can be found on the Jubula forums.
There are also the occasional quirks to look out for. For example, my current AUT shows a splash dialog on startup, and I have to dismiss it before Jubula will connect. When you're running the AUT and Jubula ITE on the same machine, it does tricky things with focus and the AUT connection can get messed up quite easily in my experience.
I've also had times when the AUT name hasn't shown up in the Running AUTs view, but I can still perform object mapping and run test suites with no problems. If everything seems to be set up correctly, it's worth trying a couple of times in case it's just a quirk messing with you.
I know I'm late but it might help those lost souls who need to migrate to newer versions of Jubula;
Jubula is made up of 3 components:
1.) Eclipse UI-plugin (or testexec.exe)
2.) AUT agent
3.) RC-plugin as the dependency of the AUT (Remote Control)
They are released in bundles:
Jubula 6.0 with 1.2 feature
Jubula 8.0 with 2.3 feature (Java 7 only)
My experiences with different versions of these:
UI-plugin Agent RC Result
1.2 6.0 1.2 Works (of course)
1.2 8.0 1.2 Works
1.2 8.0 2.3 Can't see AUT
2.3 6.0 1.2 Sees AUT but won't do mapping/tests
2.3 6.0 2.3 Can't see AUT
2.3 8.0 1.2 Sees AUT but won't do mapping/tests
2.3 8.0 2.3 Works (of course)
The 2.3 Eclipse UI-plugin won't start without using Java 7 JRE.
But Fabian's problem must be this:
The RC also needs Eclipse e4 Platform.
It writes nothing to log files but it won't start if you export/run your application on RCP 3.x platform. Thus you need to migrate your entire app to e4.
Im getting 2 errors/warnings when im trying to build/run my app in the simulator, the error is in the SDK i guess.
File: CLScoreServerPost.m
'uniqueIdentifier' is deprecated (declared at /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator5.0.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIDevice.h:64)
and this one in CLScoreServerRequest.m
'uniqueIdentifier' is deprecated (declared at /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator5.0.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIDevice.h:64)
I've been trying to reinstall the templates ect ect ect and nothing works.
Some one know the problem ?
Thanks
It says it right there:
uniqueIdentifier is deprecated
And so you should search for it on Google to come up with the related Stackoverflow question.
Deprecated means it should no longer be used, and it may be flagged as an error if you do use it depending on certain circumstances. My guess is that if your deployment target is set to iOS 5.0 and since iOS 5.0 deprecated that method, it's going to be an error when building an app that targets iOS 5. It's probably just a warning if you target iOS 4.x or earlier.
If you are calling that method, then don't. If that call is in a third party library, then contact the author of that library.
Try rebooting your iPhone and computer. Then, after you run your app from Xcode and as it was running on your phone, stop the task. Then, re-open the app through the phone without Xcode running any task.
I did this and did not receive any further errors, and was able to open/close from the active app area (double-tap home button), and I was able to re-launch it without any issues.
Hopefully this helps.
(I think this is in response to the proper problem)