From: Nobody on
"Norm" <NormF4(a)spoof.com> wrote in message
news:CCB4EA04-B92A-441C-9D74-C115E71EC60B(a)microsoft.com...
> You can have the app check for an update and then download it to app.path,

If App.Path is a folder under "Program Files", then your app would get an
access denied error in Windows 2000/XP/2003 Server if the user is a member
of "users" group. In Vista+, the file is redirected and you don't get an
error, but I am not sure if you can shell it.


From: Norm on


"Nobody" <nobody(a)nobody.com> wrote in message
news:uphDpGnwKHA.3764(a)TK2MSFTNGP04.phx.gbl...
> "Norm" <NormF4(a)spoof.com> wrote in message
> news:CCB4EA04-B92A-441C-9D74-C115E71EC60B(a)microsoft.com...
>> You can have the app check for an update and then download it to
>> app.path,
>
> If App.Path is a folder under "Program Files", then your app would get an
> access denied error in Windows 2000/XP/2003 Server if the user is a member
> of "users" group. In Vista+, the file is redirected and you don't get an
> error, but I am not sure if you can shell it.
>
>

That is probably true, I had forgotten that I moved my install to the public
folder. With the hassles of the program folder I just install everything to
the public folder and only use CurrentUser in the Registry.



From: GS on
> I would love to have the application download this file from the
> website automatically. It's easy to do. But I don't know how to
> restrict non-clients who have my app from also getting the file.
> Clients pay for this information. Non-clients do not.
>
> If I can find a solution to this part I would LOVE to do it.
>
> Thanks.
>
> Webbiz

Is this app licensed? If so, could you not include whether this is
available to your client in the license profile? Obviously, this
requires your licensing methodology to support this and so is why I
suggest going this route. This way, automatic download can be available
from your app but is only allowed to apps with the correct feature
enabled in the license profile.

I.E.: If LicenseProfile.HasDownloadService Then DownloadWeeklyUpdate

HTH
Garry


From: Webbiz on
On Sat, 13 Mar 2010 12:57:52 -0500, GS <GS(a)discussions.microsoft.com>
wrote:

>> I would love to have the application download this file from the
>> website automatically. It's easy to do. But I don't know how to
>> restrict non-clients who have my app from also getting the file.
>> Clients pay for this information. Non-clients do not.
>>
>> If I can find a solution to this part I would LOVE to do it.
>>
>> Thanks.
>>
>> Webbiz
>
>Is this app licensed? If so, could you not include whether this is
>available to your client in the license profile? Obviously, this
>requires your licensing methodology to support this and so is why I
>suggest going this route. This way, automatic download can be available
>from your app but is only allowed to apps with the correct feature
>enabled in the license profile.
>
>I.E.: If LicenseProfile.HasDownloadService Then DownloadWeeklyUpdate
>
>HTH
>Garry
>


My app is licensed. But here is the problem.

Say a client comes along and subscribes to my services. This client
also purchases my app. She gets a license to use the app and also
access to the file for download.

Later, however, she discontinues the services but wishes to continue
using the app. That's fine, she paid for it. However, the app is still
licensed to her and so she'd still have access to the file for
download although she no longer pays for that. That would be
unacceptable.

The app is licensed indefinitely and does not expire unless the user
moves it to another computer or does a major change to the system (ie.
memory, hard drive, mb, etc.). Then the user simply visits the site
and fills out the form there for a new registration key and gets it
via email.

I've been using this approach for 10 years successfully.

So as you can see, I have no facility to prevent the indefinite
downloading of my file unless I periodically change its name and
release periodic updates to the app that notes this new filename.
Meanwhile, between updates the user gets my work without paying for
it.

So for now, users who pay for the work must access the site with their
username and password and then click on the link to install the weekly
file that way.

Webbiz
From: Webbiz on
On Sat, 13 Mar 2010 06:02:38 -0700, "Norm" <NormF4(a)spoof.com> wrote:

>
>
>"Nobody" <nobody(a)nobody.com> wrote in message
>news:uphDpGnwKHA.3764(a)TK2MSFTNGP04.phx.gbl...
>> "Norm" <NormF4(a)spoof.com> wrote in message
>> news:CCB4EA04-B92A-441C-9D74-C115E71EC60B(a)microsoft.com...
>>> You can have the app check for an update and then download it to
>>> app.path,
>>
>> If App.Path is a folder under "Program Files", then your app would get an
>> access denied error in Windows 2000/XP/2003 Server if the user is a member
>> of "users" group. In Vista+, the file is redirected and you don't get an
>> error, but I am not sure if you can shell it.
>>
>>
>
>That is probably true, I had forgotten that I moved my install to the public
>folder. With the hassles of the program folder I just install everything to
>the public folder and only use CurrentUser in the Registry.
>
>

For my app, I just created a data folder under \My Documents.

What I find interesting, however, is that my app creates a directory
under the app directory for storing the charts. So it appears that the
app can access read/write within \Program Files. I guess once it is
installed it is considered 'the man' and can write to these restricted
zones. ??

Webbiz