Is UniObjects supported in UniData 8.x? - unidata

We integrated with UniData in 2013 using UniObjects for .net and we tested against UniData 7.3. We now have a client on a newer versions of UniData (8.1) and we are having new problems with the integration.
I dug through the documentation on RocketSoftware's website and found the UniObject documents were no longer listed under the documentation for UniData 8.1 and 8.2. I also couldn't find any recent threads via search engine around UniObjects.
"UniObjects for .net Developer's Guide" is listed here:
https://www.rocketsoftware.com/products/rocket-u2/UniData-v7.2
Not listed here:
https://www.rocketsoftware.com/products/rocket-u2/rocket-unidata-v821-technical-documentation
I'm not sure if the documentation just moved and I am overlooking it on the site or if it went away entirely. My suspicion is that it's not supported anymore or won't be supported soon.
Does anyone know definitively that UniObjects is supported or not supported in 8.x versions of UniData?
Any insight around this is greatly appreciated!

Yes, it's definitely supported. I work with an application that uses Uniobjects for integration extensively and it works the same as ever with 8.1 on Linux. The documentation is kind of a mess and keeps moving around, but the functionality is definitely still there.
There were security/encryption changes a few years ago, so the parameters around that are a good place to start looking. There's also a debug flag to check what's happenning - serverdebug.
https://groups.google.com/forum/#!topic/u2-users/okE3-TL_mvE was a recent thread on u2users group, it may be worth asking in that forum to get more responses too. It's a friendly bunch.

Related

Migrating sitecore 7.1 search to sitecore 8.0

I am supposed to migrate a website from Sitecore 7.1 to 8.0
I am mainly concerned with Lucene Search and indexing part of search functionality which is to be migrated as well.
I just need a heads-up for errors and bugs for the same and a question (for which no answer was found on web) is that will the search functionality be severely affected by the migration? what care should be taken while migrating?
Any helpful and relevant links are appreciated.
From what comes into my mind, there were certain changes in search configuration
contentSearch/configuration/defaultIndexConfiguration/analyzer
has moved to:
contentSearch/indexConfigurations/defaultLuceneIndexConfiguration/analyzer
there were also changes in ContentSearch namespaces
Also check EncodedNameReplacements setting for media library as it may break some of your links.
If you are using modules - check modules compatibility table by this link https://kb.sitecore.net/articles/541788 as some of them may not yet be available for 8.0. Sitecore.Kernel is now on .NET 4.5 so please keep .NET version updgrade in mind as well
I usually get two clean installations with following versions and check configuration changes in diff tool, where applicable, you may find this practice helpful as well.
Please go carefully through upgrade notes from Sitecore and consider if they have to be performed on your solution. Official upgrade notes to 8.0 can be found here https://dev.sitecore.net/en/Downloads/Sitecore_Experience_Platform/8_0/Sitecore_Experience_Platform_8_0.aspx (but you may need SDN account to access that)
Some other useful references:
https://theagilecoder.wordpress.com/2015/03/09/keystone-considerations-when-upgrading-to-sitecore-7-5-or-sitecore-8/
http://laubplusco.net/quick-tip-upgrading-sitecore-fast-easy/
http://www.velir.com/blog/index.php/2015/06/25/the-art-of-the-sitecore-upgrade/

What is the difference between Lazarus and CodeTyphon

Firstly, I saw some topics about these two but weren't my answer.
I'm looking for a good FPC(Free Pascal Compiler) IDE on GNU/Linux.
There are some IDE's like Lazarus and CodeTyphon. I need suggestion to choose one of those.
I've tried Lazarus once but all windows was separated. It looks messy and not interesting.
I would like to know what are the distinguishes between these two ?
I would like to know advantages / disadvantages each of those. Thank you
CodeTyphon is a distro of Lazarus, like Ubuntu and Debian are distros of Linux.
CodeTyphon comes with a large package of components and plugins, that otherwise you would have to google and download and install.
CodeTyphon have their own idea what are stable versions and what are not stable yet for both of FPC (compiler) and Lazarus(IDE). Whether their assessment is better or worse than upstream's Lazarus Team's, I don't know.
What about one-single-window plugin, it is work-in-progress and it doesn't seems to me it is ready for production use, no matter would you get it as part of CT or download and add it to vanilla Lazarus. However maybe it better works on Linux than on Windows, I don't know.
There were however issues with code legality in CT grande bundle. It is widely believed that Orca (if I remember the name) violates copyrights of glScene/vgScene, which also happened in early Delphi FMX releases but was fixed by EMBA later. There also were disputes in FPC forums/wiki about CodeTyphon pirating some open-source components. See answer by Peter Dunne below.
Your question is akin to asking the difference between Linux and Ubuntu. Lazarus is an IDE/component library, based on FreePascal (FPC). And CodeTyphon is a distribution of Lazarus and FPC. So CodeTyphon is just one way to install a functioning installation of Lazarus.
Lazarus uses the same floating window design as older versions of Delphi. Installing from CodeTyphon won't change that.
Myself and several friends highlighted several licensing issues with codetyphon
most of which could have been corrected by sourcing the included files from known good source and ensuring the correct license headers were included
PirateLogic refused to correct the issues which means they are using code in direct violation of the original license terms
The fact its open source code does not change the fact they are pirating the code by not including the correct license even after the issue was highlighted
I also found several instances of copyright code included which appears to be proprietary and not FOSS at all
They also changed the path & file names on some libraries so that source is no longer compatible with standard lazarus/component installs
This in my view is totally illogical
These 2 factors heavily undermine what was potentially the best FPC/Lazarus distro
Hardly professional
Lazarus can be a daunting installation process due to it's nature as a cross compiling environment. You don't just download an installer and click ok. A typical "installation" is actually a bootstrap FPC compiler doing a three-pass compilation of an "install". There are plenty of good installation scripts/methods from the official Lazarus/FPC team and in the community for a . But, understandably, the installation process is a skill in itself.
CodeTyphon is a a different/separate branch of an installer system, which is more of a utility suite/tools/third party code compilation library. If you want the simplest installation experience go with CodeTyphon. It has the nice graphical front end for managing the compiler. You can conveniently do the fancy stuff like build "cross-compilers" for almost every "target" operating system out there. It also is jam packed with hundreds of the best components/libraries pre-installed. It is a very actively maintained project and very professional. A whole lot of work is done for you.
Even if you want to be learn the low level compiler capabilities, CodeTyphon is a good place to start. It is written in FCP/Lazarus and is open source. Simply study it as "working demo app" and the other info on the compiler details. If you crash it, at least you don't have to learn to climb the hill. You get to get to start from the top and lose control on the way down. Start from scratch (and a three hour reinstallation) Hahaha
Lazarus also has a package "AnchorDock" which allows you to dock all the windows into one. Either install the anchor dock design package after installing Lazarus, or install Lazarus using the script at getlazarus.org which will do it for you.

D3DXCreateFont Alternatives on Windows 8?

I'm playing around a little bit with a hooked DirectX 9 application. As you may know, the D3DX framework has been deprecated in Windows 8. Microsoft advises us to "investigate alternative solutions to working with the Direct3D API". What are alternative solutions to using the handy D3DXCreateFont in Windows 8? I am working with DirectX version 9. If I am still able to reference the D3DX framework somehow in Windows 8, this is my preferred solution.
Use D3DX.
In this particular case, because you are hooking an application already using DirectX 9, using the libraries and resources provided by that version of the API is your best solution. When working with D3D9, using D3DX for the utility functions is perfectly acceptable and recommended practice.
The recommendations apply to software designed for Windows 8. While your software may be intended to work on that platform, hooking into applications that was not imposes significant restrictions. You have to work with what's already in use, and in this case, D3DX is going to be far more compatible than trying to rope in new libraries. In fact, given how many D3D9 and earlier apps use D3DX, there's a good chance it's already in use, and you may be able to just reuse that.
Note that this does not mean the D3DX DLL(s) you need are present; depending on the application, there may only be a single version present, so you may need to provide the DLL(s) or installer.

OSX + VB.Net, briefly what's required to port my program from windows, perhaps by mono?

I have an order entry system which was developed using vb.net it uses an ms access database.
I think I might be able to use mono?
I'll need an IDE if possible.
Can someone tell me what I'll to download and what problems I might face, also any suggestions.
You can use MoMA to determine how well your application will run on Mono. It will analyze the app and tell you of any potential compatibility issues. As far as IDE goes, MonoDevelop would work, but depending on the compatibility with Mono, you might be able to just continue to develop it on Windows. Since Mono is just an implementation of the CLR you may not have to make any code changes at all.
Mono supports ODBC for database connections, but you would have to install an ODBC driver (Such as MDB Tools).
I think I might be able to use mono?
Porting applications can be tricky, generally it can go two ways:
- Get it running with minor tweaks.
- Stop trying and start developing from scratch.
MoMA helps, but you never know for sure until you try :)
Checkout MonoDevelop for Mac OSX:
http://monodevelop.com/

What happened to ManagedSpy?

ManagedSpy is supposed to be the .NET equivalent of Spy++, but somehow the download page is now not availeble any more.
Anyone who knows why?
Anyone that knows a replacement?
--jeroen
I've cloned the original ManagedSpy source code and maintaining the code in modern environments (for example, ported it to .NET4).
See project on GitHub.
You can still download it here, but the original website seems to be gone. There is however still an article in MSDN (from 2006) about ManagedSpy.
I've cloned the ForNeVeR's ManagedSpy source code and changed a bit to support 64-bit process. see https://github.com/slimzhao/ManagedSpy
Is there a newer equivlent tool? ManagedSpy fails completely on .NET 4.0 enabled machines because Native Images existing under \Windows\Assembly* and it tries loading those as .NET assemblies and fails.