[Casper] Adobe Web Products - Was: (no subject)
Daniel Farnworth
daniel.farnworth at thecreativepartnership.co.uk
Fri Jun 15 08:08:06 PDT 2007
Hmmm... Likewise we have some machines that require the full Web Standard
Suite in addition to Design Standard, and some that only require Flash Pro
in addition to Design Standard. Our Web Standard and Flash Pro's are
licensed independently so we need to serialize both, but when we come to
install Flash after the web suite it refuses to install as it says it
clashes. Any ideas???
Cheers
Dan
UPDATE: I get likewise refusal the other way round, it offers to install the
other apps, but not Flash...
On 15/06/2007 13:10, "Daniel Farnworth"
<daniel.farnworth at thecreativepartnership.co.uk> wrote:
> Sorry to keep bringing this one up peeps...
>
> Does anyone know what the situation with including After Effects 7 is?
>
> It still uses all the old versions of various apps, Help Center instead of
> Help Viewer, Bridge CS2 instead of 3 etc. Does this mean that perhaps it
> uses a separate license database also?
>
> Should I build this as a completely separate and independent package? Or is
> this going to cause me more problems?
>
> Cheers
> Dan
>
>
> On 11/06/2007 16:30, "Daniel Farnworth"
> <daniel.farnworth at thecreativepartnership.co.uk> wrote:
>
>> Thanks, exactly as I suspected, but with lots more useful info
>>
>> Ta
>> Dan
>>
>>
>> On 11/06/2007 14:34, "Ernst, Craig S." <ERNSTCS at uwec.edu> wrote:
>>
>>> The formerly known as Macromedia products are integrated with the suites.
>>> The
>>> biggest dependency is the licensing database that manages all the
>>> applications. That is the common part to all of them, whether it's CS3
>>> Design
>>> Premium or CS3 Web Standard (which only adds Fireworks and Contribute to
>>> what's already in Design Premium).
>>>
>>> The issue, and I'm sorry if I'm repeating, is the licensing database, it's
>>> not
>>> really designed to handle modular packaging, well. The other shared files
>>> aren't really a big issue.
>>>
>>> For example, let's say you wanted to deploy CS3 Design Premium. Ok, so you
>>> pack up CS3 Design Premium and push it out. Now you decide you want to add
>>> in
>>> the two pieces of CS3 Web Standard, so you make a pack of those, and then
>>> deploy that. Well, you broke your Design Premium install because the
>>> licensing
>>> database was overwritten that had the Design Premium license information in
>>> it
>>> with a licensing database that only has Web Standard information.
>>>
>>> How do you get around that, well that's why we have to make an
>>> Adobe-Required
>>> package out of both suites. We have to install Design Premium and install
>>> Web
>>> Standard, fire up all the applications, enter the licenses for both suites,
>>> and then pack it. We break out the applications into packages and leave the
>>> rest as the Adobe-Required pack. Now we can deploy just what the end user
>>> wants. If they want Dreamweaver and Photoshop I can push out DW, PS, and the
>>> Required pack (mainly to save disk and bandwidth). Keep in mind that they
>>> are
>>> still eating up a Design Premium license.
>>>
>>> Now if this method doesn't sit well you can do some xml scripting (I think)
>>> of
>>> some sort (it's what the installers do when you install the software) to
>>> handle updating the licensing database correctly to deploy packages if you
>>> didn't want to pack them all together, but I don't know anything about that.
>>> It all boils down to the licensing database (that's the problem) and if you
>>> plan to use multiple licenses. If not, no worries.
>>>
>>> Craig
>>>
>>>
>>> On 6/11/07 7:01 AM, "Daniel Farnworth"
>>> <daniel.farnworth at thecreativepartnership.co.uk> wrote:
>>>
>>> Just following up from this, now that Adobe own all the old Macromedia
>>> products, how does this affect packaging of Flash, Web Studio etc?
>>>
>>> Does it follow, that these now rely on the same common files and shared
>>> libraries that the other CS apps (Pshop etc) do?
>>>
>>> Should we follow the same procedure no matter what Suite?
>>>
>>> Cheers
>>> Dan
>>>
>>> _______________________________________________
>>> Casper mailing list
>>> Casper at list.jamfsoftware.com
>>> http://list.jamfsoftware.com/mailman/listinfo/casper
--
Daniel Farnworth
IT Manager
The Creative Partnership
daniel.farnworth at thecreativepartnership.co.uk
http://www.thecreativepartnership.co.uk
Tel: +44 (0)20 7439 7762
Fax: +44 (0)20 7437 1467
PGP Public Key available<BR>
The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorised to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify postmaster at thecreativepartnership.co.uk immediately and then delete this email from your system. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of The Creative Partnership. The Creative Partnership has taken every reasonable precaution to ensure that any attachment to this e-mail has been swept for viruses. However, The Creative Partnership cannot accept liability for any damage sustained as a result of software viruses and would advise that you carry out your own virus checks before opening any attachment.
More information about the Casper
mailing list