In reference to Outlook Add-in Commands, I am confused about VersionOverrides 1.0 vs 1.1. I see examples with a 1.1 VersionOverrides element embedded in a 1.0 VersionOverrides element in order to get the newer mobileformfactor support, but what is stopping me from replacing schemas.microsoft.com/office/mailappversionoverrides with schemas.microsoft.com/office/mailappversionoverrides/1.1 in my existing desktopformfactor add-in and adding a mobileformfactor entry to that?
Must 1.1 be embedded in 1.0? What would break if 1.0 was swapped out for 1.1? Are some platforms not ready with 1.1 support?
I have searched the web but cannot find good documentation about this.
...xisting desktopformfactor add-in and adding a mobileformfactor entry to that?
The following resource explains that: Add support for add-in commands for Outlook Mobile
Must 1.1 be embedded in 1.0?
Yes.
What would break if 1.0 was swapped out for 1.1?
You'll get something like this when installing misconfigured manifest: "This app can't be installed. The manifest file doesn't conform to the schema definition."
Are some platforms not ready with 1.1 support?
Hmmm ... this is weird question. This should be opposite: you, as developer, choose what what manifest version your app needs to support. You need VersionOverrides 1.0, because the child, VersionOverrides 1.1, does not inherit any values from the parent and they have to be there.
I have searched the web but cannot find good documentation about this.
Here you go: VersionOverrides element
Related
I'm using Mule Server 3.8 EE which brings commons-lang 2.4 with it. A third-party library in my project needs commons-lang 2.6, because it uses a method that was introduced in this version.
So when I just start my application, I get a java.lang.NoSuchMethodError
Is there a way to update the dependency in the runtime? What I tried so far:
including commons-lang 2.6 in my app -> no effect, the one from the runtime is picked up first
replacing the jar directly in the runtime -> errors in studio, that the 2.4 jar is missing
so maybe i am late BUT -- this is your answer. Add the libraries that are newer in the jar distribution to the Build Path. Under Java Build Path screen you should see the libraries listed. I needed to use Apache http-client 4.5.6 and that's very interesting because it brings with it a lot of other dependencies, so your question was VERY relevant. The solution is to rely on JAVA (and not mule -- oops Anypoint or whatever) conventions and make sure the JVM loads my class files first. Then, it won't load the old ones from mule's jar. And so I went to the tab Order and Export, and moved Mule to the bottom. This simple, trivial change makes it work. I think if we would work with command line and vim, we would all know this. But all the IDE gui and everything else makes us forget the simplest things. Please use it in good health. :)
While changing the dojo version from 1.3 to 1.7.3, I simply replaced all my dojo 1.3 folder files with dojo 1.7.3. After rebuilding my web application, I am getting error hxrFailed at dojo.js, line no 15.
What is the wrong that I am facing here? Do I need to change any existing code. Is there any document to refer for all the required changes.
Please help me to get out from this issue.
Thanks,
Sridhar.ch
Lots changed and there are some lengthy tutorials to help you migrate. Check out the documentation tab on Dojo's website:
1.x to 2.0 migration guide:
http://dojotoolkit.org/reference-guide/1.8/releasenotes/migration-2.0.html
Updated buildsystem tutorial:
http://dojotoolkit.org/documentation/tutorials/1.8/build
In theory the current (1.8) build system is backward compatible until 2.0, but in practice I'm not sure it is 100% backward compatible because my 1.6 build profile didn't work with 1.7.x and up. I didn't try that hard to get it to work though.
I have gone through the same. the xhrFailed error occurred for me for multiple reasons. One of the reason was a missing a file in the define as below:
define(["something/was/missing/here"],function(){});.
Another cause for the same error occurred was when a folder in a path of a dependency was renamed but not updated in the application build profile. (This case only if your are doing custom builds).
See if that is the case!
Lotus Notes 8.5.3 uses dojo 1.5.1. However I want to use dojo 1.6/1.7 library in my NSF database. How can I do it? I tried to use the technique suggested by Keith Strickland in his blog but no luck.
I need to include the dojo library in NSF database and not on server.
The reason I want to do this so as to use the advanced Dojo Mobile libraries (from dojo 1.6/1.7) in my XPages.
UPDATE: I even posted this question on XPages forum some time back but no replies.
The Domino 8.5.3 server uses Dojo 1.6.1 for XPages. You should see this if you view the HTML source of a test application.
As an example, I see this in one of my applications:
"/xsp/.ibmxspres/dojoroot-1.6.1/dojo/dojo.js"
If you are going to create apps using Dojo Mobile then take a look at the Extension Library and the latest Upgrade Pack 1 for Domino 8.5.3. Both includes XPages Mobile controls.
Per's correct that the Dojo plugin that is loaded by default is 1.6.1 (the ".1" is because it includes IBM-specific code and this means it differentiates it from anything a developer has added in).
The files in the js folder on the server / client are 1.5.1 and this is needed for iNotes.
You can change the Dojo version in the xsp.properties by setting xsp.client.script.dojo.version in Package Explorer. Incidentally UP1 offers a nice visual editor for the xsp.properties file.
However, currently if you change this setting you need to uncheck "Use runtime optimized javaScript and CSS resources" or it will still use the plugin. I noticed this too late for anything to be done before the Gold release.
If you add 1.7 files to the server and include the IBM folder from 1.5.1 it may work. AFAIK there's no way to get the IBM folder from the plugin code.
See my blog post for more details: http://www.intec.co.uk/domino-8-5-3-greater-power-over-dojo-thanks-ibm-for-your-work/
I am looking for a good DNP3 library for .NET/VB applications.
Any recommendations?
Thanks,
The open-dnp3 project has recently added .NET bindings:
code.google.com/p/dnp3
Automatak maintains a fork of the opendnp3 library with .NET bindings:
http://automatak.com/opendnp3/
We have heard from users that opendnp3 significantly outperforms the TMW library for large master integrations.
Opendnp3 is Apache-licensed (free-to-use), but commercial support is available if you get stuck.
All I could find with a Google search was Trianble MicroWorks' .NET Protocol Components.
It looks like they're not exactly on top of the latest technology (it lists itself as .NET framework 2.0 compatible), but I wasn't able to find anything else that looked terribly promising.
I've managed to build the Automatak version of this library:
https://github.com/automatak/dnp3
and use the .NET bindings with C#, though they would work equally well with VB.
OpenDNP3 from automak is available in Nuget, but you should install 32bit openssl application to able to load it.It installs two required .dll files.
I'm working on a cross-platform solution currently. The solution uses XmlMtomReader and XmlMtomWriter from .NET framework 3.0.
Now i need to know if these two classes (and all the nessasary infrastructure around them) are fully supported in Mono project from the porting-it-to-linux point of view. :)
You can check it on the mono status:
http://go-mono.com/status/
You can also check your code using the mono migration analyser
http://www.mono-project.com/MoMA
I checked they are currently not implemented
The APIs are available on the current Mono 2.6 preview, but they are not available on the 2.4 release (the current official release).