Plug in compatability between LR versions

Hi,
I have LR3, and saw a plug in to export from LR2 to Shutterfly. Can I safely assume that plugins are forward compatible, or am I limited to plug ins that are specifically tagged for LR3?
thanks,
ray

Answered my own question by seeing a similar question in a previous post. Yes it is compatable in this particular case. I suspect mileage may vary from plug in to plug in in terms of being verified to work on later LR versions. It loaded and worked like a charm. Sorry for the noise.
ray

Similar Messages

Plug in compatability between BW plugin in R/3 and BI - R/3 upgrade to ECC6

Hello,
we are running SAP NetWeaver BI 7.0 Release 700 Patch 19.
Our underlying R/3 system is still 4.6C with plugin 2004_1_46C ( yes, I know it is time )
We are upgrading R/3 to ECC6 with plug in P701 Patch 3.
Questions:
1.) I would like to know where exactly I can see which ECC6 plugin is copmpatible with our BI Version.
2.) Did anyone who has upgraded to ECC6 experience any particular issues when upgrading the plugin?
3.) Sense check of approach - so far the simplistic idea from a BW perspective is:
New R/3 system has been created and connected to BW :
1.)     In BW ACTIVATE SOURCE SYSTEM
2.)     In source system connection option : Replicate datasources and activate
3.)     Transfer global settings u2013 first simulate then update tables u2013 no rebuild should be necessary
Before the Plugin P 701 in the R/3 ( ECC6 ) system can be upgraded the BW delta queues need to be cleared in the source system ( R/3.)
4.)     Clear out V3 queue either via BW as part of the jobplan ( or manually via RSA7 but would mean loss of data )
5.)     After run of batch schedule during posting free period check in RSA7 for entries in delta queue - should be empty
                     now.
6.)     Does the clearing of the delta might need to be run twice to clear the queue completely ?????
8.)                 Deactivate logistics cockpit via SBIW ...LEBW ( is this mandatory ? )
9.)                 If delta queues are empty and the logistics cockpit is deactivated then upgrade the plug ins in R/3
10.)               Then repeat step 1-3 and reactivate the logistics cockpit again
Is this it?
Many thanks for advise on this.
Regards
ChrisAC

SAP Note : 153967 and
https://service.sap.com/r3-plug-in should give some information on plug in compatibility...
8.) Deactivate logistics cockpit via SBIW ...LEBW ( is this mandatory ? ) - I think you just need to desachedule the collection jobs alone and not deactivate the LO Extractors and activate them once again...
Edited by: Arun Varadarajan on Oct 9, 2009 11:43 PM

Nican backwards compatibility between nican versions 2.1.3 and 2.6

Hello folks,
I have inherited a VC++ application that uses nican. It was apparently compiled using nican version 2.1.3 (assumed to be true because the VC++ program works with nican 2.1.3). We recently installed LabVIEW 8.6 (including nican 2.6) and the VC++ program no longer worked. After uninstalling nican 2.6 and reinstalling 2.1.3 the program works again. This is fine except that for new development, we would like to use the nican 2.6 (the latest we presume?)
This raises a couple of questions:
1. Is nican 2.6 expected to be backwards compatible with 2.1.3?
2. If the answer to the question above is "yes", then can anyone offer any suggestions on why the VC++ program would no longer work when nican 2.6 was installed?
3. If nican 2.6 is not backwards compatible with nican 2.1.3, where can I find the necessary documentation (e.g. well documented .h files etc) to begin trying to decipher what is and isn't compatible so I can make the necessary changes?
Any help is greatly appreciated.
Best Regards,
Chris

Hello B2k,
Thanks for the information. I wasn't too sure where to start, so I don't have any more information yet. The application does not report any errors, it just doesn't "do" anything. For example, when I connect to the UUT using the VC++ application, the first thing I would normally do is read the EEPROM (over CAN), but this doesn't work with NICAN 2.6 installed.
It looks like NI-Spy may very well help me determine where (i.e. what calls) are failing, thanks.
1. Do you know where NICAN 2.6 puts nican.dll and nican.h?
2. You explicitly stated that NICAN 2.6 should be backwards compatible with 2.1.3, but IF something has changed in the interface (e.g. a function signature etc.) do I need to search the nican.h files to try to find the difference, or do you know of another document that lays them out more clearly? (I found several documents/revisions on the NI website (e.g. "NICAN Programmer Reference Manual" and "NICAN Hardware and Software Manual and Specifications"), but I don't have any idea which document/revision goes with which version of NICAN?
Thanks for your time and the helpful information!
Chris

Check binary compatibility between 2 Jars

Hello,
we have a Java API to our repository product. Is there a way to check binary compatibility between different versions of that API? The problem is that the interfaces evolve and sometimes changes are necessary. So we already had the problem that different versions are incompatible.
I found just one tool: japitool. But it does not detect the latest problem we have.
Thanks in advance
Torsten

I mean the facts and rules described in chapter 13 of the Java language specification (Binary Compatibility; http://java.sun.com/docs/books/jls/second_edition/html/binaryComp.doc.html#44872).
Torsten

My APE11 gets an Unable to use plug-in It's not compatable with this version of Photoshop

My APE 11 will read my Canon 70D raw file since I used the 8.3. In the organiser but as soon as I got to Edit the Raw file it just come up " Unable to use Camera Raw Plug-in" " It is not compatable with this version of Photoshop" No photo in the screen at all just a blank area with the raw sliders. And the box with the wording unable to use etc.

PortalPacific wrote:
…Here is the file im having trouble with. You can download it here if you are interested in taking a look: …http://portalpacific.net/movieposter.psd
I downloaded it and looked at it. Even Graphic Converter can't recover any pixels or meaningful data, just some general information:
In my experience, if GraphicConverter can't open it, nothing will.
Your file is toast Sorry.

I have a web site built by Yahoo Web Site Builder which does not have a Mac version, is there any compatability between Iweb and the old Yahoo program?

I have a web site built by Yahoo Web Site Builder which does not have a Mac version, is there any compatability between Iweb and the old Yahoo program? If not how do I clear off the old site so as to re publish with Iweb.

iWeb cannot import published files so you would need rebuild the site.
Yahoo hosting is notoriously poor and their tech support is awful. I would suggest you look for new hosting and start afresh. Some pointers for choosing hosting...
http://www.iwebformusicians.com/iWeb/Website-Hosting.html
If you do choose to go this route, transfer your domain name registration away from Yahoo to your new host.

Premiere CS6 and CC: any compatibility issues working back and forth between both versions?

Hello,
What are the compatibility issues with Premiere CS6 and CC versions? Can the user go back and forth? I run a computer lab at a college and we will be upgrading to CC but many students will still be using the older CS6 version of Premiere until we update all the computers.... Will students run into problems?
Thanks,
dmichael

My concern is going back and forth between the versions... I read somewhere there are compatibility issues with Premiere....Can the user working in CC go back to premiere CS6? and vice versa?
Thanks,
dmichael

Compatibility between CS3 and earlier versions?

As the web developer I have Contribute version 3, but some of
my new clients
will be buying the latest Contribute CS3 to update their site
pages. Can I
still set up their roles and editing rights for a site and
create a
connection key to send to them that will work for them in
Contribute CS3
without difficulty? And can either of us still edit the site
pages,
regardless of the fact that we are each using different
versions of
Contribute?
In conclusion, are there any backward compatibility issues I
should be aware
of between the newer version and older versions of CS3 when
administering,
and connecting to, the same website?
Thanks in advance.
(Please reply to forum. E-mail address is bogus to prevent
spam)

Thanks for the advice.
"ThinkInk" <[email protected]> wrote in
message
news:f0sa43$dvh$[email protected]..
>I had the same problem when C4 arrived and I could'nt
purchase C3 for my
> clients.
>
> The key is to use Transitional Mode (adminstrator
settings,
> compatibility),
> here's wat the HELP says:
>
> --------------------------
> Enabling compatibility with older versions of Contribute
> Contribute 4 offers administrators two compatibility
options--one that
> allows
> users with earlier versions to work on the website, and
one that does not:
>
> Transition Mode
> In this mode, users of earlier versions of Contribute
can continue working
> on
> the website, along with Contribute 4 users. This lets
you evaluate the new
> version and set up new roles and permissions without
disrupting users with
> earlier versions of Contribute.
>
> Compatibility Mode
> In this mode, all users must use Contribute 4. Users
with earlier versions
> cannot work on the website.
>
> Contribute 4 starts in Transition mode by default when
you migrate from
> Contribute 3. Use this mode temporarily; when you?re
ready, transition all
> users to Contribute 4 and enable Compatibility Mode.
>
> To enable Compatibility Mode:
> In Contribute 4, select Edit > Administer Websites,
and then select a
> website.
> The Administer Website dialog box appears.
>
> Select Compatibility from the category list on the left.
> The Compatibility options appear in the Administer
Website dialog box.
>
> Select Compatibility, and then click Close.
> After you enable Compatibility Mode, all users connected
to the website
> must
> use Contribute 4.
>
> ------------------------
>
> It's really better to upgrade yourself to the newest
version, so you know
> what
> extra options your clients have and you can support
them. I managed to get
> both
> C3 en C4(I purchased the upgrade) running on my PC, so
maybe that's also
> an
> option.
>
> grtz. Hayo
>

I like ti known about compatibility between Windows 8 and iTunes

I like ti known about compatibility between Windows 8 and iTunes

It works for some and not for others.
At this time, there is no publicly available version of iTunes that is supported on Windows 8.
Only Apple knows when that will change.

Compatibility between CRM 4.0 and IS-U 4.64

Hi,
My company is using SAP IS-U 4.64 and is studying the use of SAP CRM. Does there is any problem of processus compatibility between these two versions ?
I don't find any document on the market place or in sdn. Does there is a document that shows the optimization for cross application use of SAP ?
Thanks
Thomas

Hi Gaurav,
I've dealt with both realities (specially in IC Webclient) and from the configuration point of view and in my opinion, it is basically the same.
For me the main change is that, in IC webclient scenario, instead of you do some customizing in a XML code, in CRM5 you'll do it by configuring tables.
In CRM5, you'll have some nice functionalities that CRM4 doesn't have (e.g.: You can choose with channels your transactions are allowed, Email Workbench, ERMS categorization is time dependent, and so on...), but the big jump is given when you compare CRM5 to CRM6 (or CRM 2007).
Kind regards,
Bruno

Compatibility between SAP ERP upgrade with SAP PI 7.3 sp12

Hi Experts,
Our SAP ERP system getting upgraded to ECC 6.0, ehp 7, SS7 and we need to check its compatibility with the current SAP PI version(7.3 sp09) and its future upgraded version which is sp12.
Would any one kindly help me to track the PI system compatibility with the ERP upgraded version and its adverse effect(if any) on interfaces between PI and ECC system?
Thanks
Navneet.

Hi Navneet
If your PI is already on 7.3, it is compatible with ECC6 EHP7. For more details refer to the SAP note that is mentioned in my reply on the thread below.
Compatibility between PI 7.11 and Ehp7 for ERP6
Rgds
Eng Swee

Still no compatibility between Storage Client Library v3 and emulator?

Hi,
According to this blog post:
I'm apparently unable to post a link, but here's the text from the blog. I'm sure you can find it via google if interested.)
<<<<
Storage Emulator Guidance
As mentioned above an updated Windows Azure Storage Emulator is expected to ship with full support of these new features in the next couple of months. Users attempting to develop against the current version of the Storage emulator will receive Bad Request
errors as the protocol version (2013-08-15) is unsupported. Until then, users wanting to use the new features would need to develop and test against a Windows Azure Storage Account to leverage the 2013-08-15 REST version.
>>>>
So it seems there was not compatibility between the storage emulator and Storage Client Library v3. I'm wondering if that is still the case. I get a 400 error when calling container.CreateIfNotExists() when pointing to local storage, but no problem pointing
to production storage. I'm using SCL v3.0.2.
Thanks...
-Ben

Hi,
Please see
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/c961d0df-e6ab-4563-958c-b3646ee2cd9d/the-value-for-one-of-the-http-headers-is-not-in-the-correct-format?forum=windowsazuredevelopment#16892f11-498d-4975-aa4b-adfa12b03fea
Here is a snippet of this thread.
Storage Emulator 2.2 is currently incompatible with Storage Client Library 3.0.0.0. This has been mentioned in Storage Team Blob as well:
http://blogs.msdn.com/b/windowsazurestorage/archive/2013/11/27/windows-azure-storage-release-introducing-cors-json-minute-metrics-and-more.aspx (Please
read "Storage Emulator Guidance" section towards the end of the post).
It may be fixed in the next version.
Hope this helps
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

POF compatibility across Coherence versions

Dear all,
I am very interested in using POF serialization to synchronize two Coherence grids via JMS for its performance and because the OO<->bytes serialization is already paid exchanging data between the business logic and the backing map.
Before going in this direction, I would like to better understand POF characteristics (in addition to the wiki docs*) :
- Will there be a POF compatibility between Coherence 3.5 and the forthcoming versions ?
For example, will a POF written with Coherence 3.5.3 will be understandable by Coherence 3.6 ? 4.x ? Will the reverse be also true ? Will a POF written by Coherence 4.x be understandable by Coherence 3.5.3 ?
- Is there a plan to make POF independant of Coherence ? Will it be possible to use POF in a pure weblogic-or-tomcat web app ? Will there be a downloadeable pof library with the associated licensing ?
Thanks,
Cyrille
* http://coherence.oracle.com/display/COH35UG/The+Portable+Object+Format

cyrille.leclerc wrote:
Thanks for the insight Robert,
Having such annotations in September would be very interesting for us.
In addition to the classical *@Entity*, *@Basic*, *@Id*, *@IdClass*, I would like very much to have :
* *@OneToMany* and *@OneToMany* to easily navigate in my partitionned entities (relations only possible between sub entities of the "root" entities that are put in the grid )
* *@Version* for optimistic locking
* AccessType field/getter in case I must do tricky things during my serialization
* *@Index* to index fields declaratively
* My super dream would be to have a *@Lob* annotation to tell the grid to store my very big fields with coherence transparently offloading this voluminous data outside of the heap memory and the RAM. I currently look at using a nio-file-manager style "lob-cache" just next to my "entity-cache" with colocalisation/keyassociation between the two.
That was my whishlist :-)
thanks again,
Cyrille
Cyrille Le Clerc
[email protected]
Hi Cyrille,
my annotations do not work like JPA. The annotation processor which processes it just generates PofSerializers for them.
Any kind of navigation-like code is totally orthogonal to them. Practically you can write your navigation code into your get methods (or implement them in utility methods and call on them from the getters) if you like (I don't usually like such coding style because it introduces the n+1 problem), and annotate your to-be-serialized attributes and the annotation processor takes care of generating PofSerializer implementations during build time.
Obviously, for the .NET/C++ artifacts, some additional customizability needs to be introduced to reproduce such navigation methods you may have, but that is still the future, and I don't see that such a critical feature. I don't really like resource modification code in data class operations. It brings back the days of EJB 1 Entity beans again.
The @Index annotation could be taken care of by another annotation processor which may or may not be aware of my POF Serializer runtime library, although I do see added value in integrating such indexing support into the generator (generate proper extractors leveraging certain features of my attribute serializers)
What you mentioned for AccessType is likely supported by the existing serializer annotations (pre/post serialization/deserialization hooks, getter/direct field access, immutable factory class support for deserialization).
For blob you should also look at nio-memory-manager and partition-aware backing maps (it increases the total NIO memory you can leverage).
Best regards,
Robert

Backwards compatibility between DWCS3 and DW8

I am purchasing the CS3 Web premium and plan to only install
in on the new desktop I will purchase. Most of my design work will
be done on that system but I will occasionally need to work on
files when traveling on my laptop which will only have DW8 (not
upgrading that system just yet). Will there be any compatibility
issues in working on the same file between both versions, or am I
stuck only working on the desktop?
Dara

I don't see any problem with compatibility if they are static
pages and you
haven't used any of the newer features from CS3 like Spry for
example.
Nadia
Adobe® Community Expert : Dreamweaver
CSS Templates |Tutorials |SEO Articles
http://www.DreamweaverResources.com
~ Customisation Service Available ~
http://www.csstemplates.com.au
"Dara_BSI" <[email protected]> wrote in
message
news:f3o93g$ert$[email protected]..
>I am purchasing the CS3 Web premium and plan to only
install in on the new
> desktop I will purchase. Most of my design work will be
done on that
> system but
> I will occasionally need to work on files when traveling
on my laptop
> which
> will only have DW8 (not upgrading that system just yet).
Will there be any
> compatibility issues in working on the same file between
both versions, or
> am I
> stuck only working on the desktop?
>
> Dara
>

Compatibility between Exchange 2007 service packs

Hi all, I have 5 servers Exchange:
- 3 Servers CAS and HUB
- 2 Servers Mailbox server in Microsoft Failover Cluster (MSCS)
Domain Controllers are all
Windows Server 2003 SP2
The versions of Exchange 2007 SP1 servers are all:
8.1 Build 240.6
I have thought about installing SP3 and RU13 in all 5 servers for Exchange, but I'm going to install SP3 and RU13 on 2 servers CAS / HUB and the following week at the other CAS / HUB server.
Finally, the following week in the two Mailbox Servers.
Is there any problem if I miss 2 servers CAS / HUB with SP3 RU13 and the other CAS / HUB in SP1, this will only be for a few days?
Is there any problem if I leave the servidors Mailbox Servers in SP1 while CAS / HUB are in SP3 RU13, this will only be for a few days?
regards
Microsoft Certified IT Professional Server Administrator

Hi Yupikaiey.
Only thing you should be concerned is if you have CAS-CAS proxy or the Mailbox Cluster part.
Your current plan looks good. Just stay alert for any uncommon issues popping up, which would normally mean due to the difference.
If you upgrade your servers in this order, you may avoid potential service interruptions.
Details below:
Version Constrains are more of between roles of 2007-2010-2013 and not between same version SPs or RUs.
Exchange 2013 Server Role Architecture
The Past: Exchange 2007 and Exchange 2010
Our goal was to make these server roles autonomous units. Unfortunately, that goal did not materialize in either Exchange 2007 or Exchange 2010. The server roles were tightly coupled along four key dimensions:
2.This also necessitated a tight versioning alignment – a down-level Hub Transport or Client Access shouldn’t communicate with a higher version Mailbox server; in some cases this was enforced (e.g., Exchange 2007 Hub Transport servers cannot deliver messages
to Exchange 2010 Mailbox servers), but in other cases they were not (e.g., an Exchange 2010 SP1 Client Access server can render data from an Exchange 2010 SP2 Mailbox server).
The versioning restriction also meant that you could not simply upgrade a single server role to take advantage of new functionality – you had to upgrade all of them.
The Present: Exchange Server 2013
If I upgrade the Mailbox server with a service pack or cumulative update, then for a given mailbox hosted on that server, all data rendering and content conversions for that mailbox will be local, thus removing version constraints and functionality issues
that arose in previous releases.
Exchange 2007 Servicing
http://technet.microsoft.com/en-in/library/dd421853(v=exchg.80).aspx
Deployment Order
Our test infrastructure guarantees that Exchange hotfixes work across multiple server roles. The order in which you apply the update rollup to the servers is not important except if you are deploying CAS-CAS proxying. Because the update rollups are not segmented
for different Exchange server roles or for specific file configurations, apply each update rollup package to all Exchange 2007 servers in your environment.
If you have multiple Active Directory sites, and if you deploy a Client Access server in the proxy sites that do not face the Internet, you must
apply the update rollup to the Internet-facing Client Access servers
and to the non-Internet-facing Client Access servers in the proxy site simultaneously. For other Exchange 2007 configurations, we recommend that you
apply the update rollup package to the Client Access servers before
you apply it to servers that are running other Exchange 2007 server roles, such as the Mailbox server role, the Hub Transport server role, and the Edge Transport server role.
Note:
Applying service packs and update rollups to clustered Mailbox servers requires specific planning and application steps. For more information about how to apply service packs to Exchange 2007 clustered Mailbox servers, see
Upgrading Clustered Mailbox Servers to Exchange 2007 SP1 or later. For more information about how to apply update rollups to Exchange 2007 clustered Mailbox servers, see
Applying Exchange 2007 Update Rollups to Clustered Mailbox Servers.
For Patching and compatibility between versions:
Determine the service pack level of Exchange.
Update rollups are service pack dependent. For example, an Update Rollup 5 package is available for Exchange 2007 and for Exchange 2007 Service Pack 1. To determine the service pack level of Exchange, examine the
ExchangeVersion property. For more information about how to view the
ExchangeVersion property and about the build number that is associated with each Exchange version, see
Exchange Server 2007: Platforms, Editions, and Versions.
References:
How to Install the Latest Service Pack or Update Rollup for Exchange 2007
Exchange Server Updates: build numbers and release dates
We are looking at doing the roll-up to SP3
Coexistence of Exchange2007 SP1 and Exchange 2007 SP3
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Plug in compatability between LR versions

Similar Messages

Maybe you are looking for