coapp-developers team mailing list archive

[Trevor Dennis <trevor@xxxxxxxxxxxxx>]

Hi,

I think I'd still prefer them to be under Program Files if possible.
Windows admins expect applications to be in a standard place and I don't
think they care too much if it's a windows app vs web app.  Microsoft places
all their web apps under Program Files unless the user chooses otherwise.
Eg. SharePoint, WSUS, SQL Report Server.

Typically, a web app should not be changing its code files without using a
regular upgrade process like installing a new MSI.  I know some like
WordPress will update their own files though through their admin interface.
But typically they just apply the same files that the new download would
have put in anyway.  I'd never expect a good web app to require a user to
manually change the included code files.  At least, not on any sort of
production machine.  I don't see an issue with adding files to a web app
like new template files and stuff.

In either case, data files used by a web app should not be under the Program
Files directory.  Probably under ProgramData except some goof at Microsoft
decided to make it hidden which encourages people to forget to back it up.

Trev.



On Tue, Apr 6, 2010 at 10:16 AM, Garrett Serack <garretts@xxxxxxxxxxxxx>wrote:

>
>
> In the blueprints (http://coapp.org/Blueprints/Packages), I’ve outlined
> six types of packages:
>
>
>
> *Applications & Services*
>
> (PHP, Apache, Gimp, Open Office)
>
> *System tools & shared utilities *
>
> (awk, grep, etc)
>
> *Libraries *
>
> (static libs)
>
> *Shared Libraries *
>
> (DLLs)
>
> *Plugins *
>
> (PHP extensions, Apache Modules, browser plugins)
>
> *Source Code *
>
>
>
> *Device Drivers*
>
>
>
> I’ve been thinking there is another class of packages. I’m thinking along
> the lines of WebApps. I’m not sure they belong in [*\Program
> Files\<publisher>\<application>*] (like Applications), since they contain
> files (PHP, ASPX, etc) that have a high likeliness of needing
> modifications—which is heavily discouraged in [*\Program Files*].
>
>
>
> The typical installation if they are using IIS would be [*
> \inetpub\wwwroot\<application>*] but that makes a strong assumption that
> they want it in the default web root.
>
>
>
> We could make some assumptions and go with [*
> \inetpub\applications\<vendor>\<application>*] regardless of
> webserver--Apache or IIS could be easily configured to pick up the app from
> there (regardless of virtual root or virtual app directory).
>
>
>
> Ideas? Feedback?
>
>
>
> And, is there a more generic case that this is part of—packages that are
> not really executables, but large collections of files that are used to
> drive a particular purpose (and aren’t ‘documents’ either)?
>
>
>
>
>
> [image: Description: fearthecowboy] <http://fearthecowboy.com/>
>
> *Garrett* *Serack* | Microsoft's Open Source Software Developer | *Microsoft
> Corporation
> Office*:(425)706-7939                                       *email*/*
> messenger*: garretts@xxxxxxxxxxxxx
> *blog*: http://fearthecowboy.com                                      *
> twitter*: @fearthecowboy <http://twitter.com/fearthecowboy>
>
> *I don't make the software you use; I make the software you use better on
> Windows.***
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers>
> Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~coapp-developers<https://launchpad.net/%7Ecoapp-developers>
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 

Trevor Dennis