Click-Once Deployment

[Jordan S.]

I have a client that has an MS Access application that has outgrown MS
Access and it's time to migrate to something more substantial. I'm proposing
a .NET Windows Forms application.

The client is balking in part because they don't want to have to incorporate
my proposed .NET application into their desktop image. Strange, their
balking, because they *already* have deployed the .NET framework on their
desktop image.

So I don't have a lot of time to investigate, in detail, Click-once and/or
the Application Updator Block (from the patterns and practices group) - so
I'd just appreciate verification of my understanding (I'm not lazy - just
swamped right now!!! so thanks for any high-level guidance on this):

So, am I correct to claim or believe that:
1. Because they already have the .NET Framework installed on their client
image (XP Pro) that I don't need for them to install anything else in the
image - except perhaps a folder for my application and the application's
files.

2. If deployed with ClickOnce - we don't have to touch the client machines
At ALL or modify their desktop image (because we can send an e-mail to users
with a link that, when clicked triggers the complete installation.

3. Server-side requirements for ClickOnce are no more than a share that is
visible to all potential clients (with sufficient NTFS permissions to permit
reading from the share).

4. After initial deployment (via the e-mail thingie described above), the
application will update itself upon startup.

In other words - we literally don't need to ever touch the existing desktop
image if we go with ClickOnce (or Application Updator) and the app can be
deployed and updated on an ongoing basis automatically. yes?

Am I missing anything or just plain wrong about any of this?

Thanks!

 

[SP]

I have a client that has an MS Access application that has outgrown MS
Access and it's time to migrate to something more substantial. I'm
proposing a .NET Windows Forms application.

The client is balking in part because they don't want to have to
incorporate my proposed .NET application into their desktop image.
Strange, their balking, because they *already* have deployed the .NET
framework on their desktop image.

So I don't have a lot of time to investigate, in detail, Click-once and/or
the Application Updator Block (from the patterns and practices group) - so
I'd just appreciate verification of my understanding (I'm not lazy - just
swamped right now!!! so thanks for any high-level guidance on this):

So, am I correct to claim or believe that:
1. Because they already have the .NET Framework installed on their client
image (XP Pro) that I don't need for them to install anything else in the
image - except perhaps a folder for my application and the application's
files.

2. If deployed with ClickOnce - we don't have to touch the client machines
At ALL or modify their desktop image (because we can send an e-mail to
users with a link that, when clicked triggers the complete installation.

3. Server-side requirements for ClickOnce are no more than a share that is
visible to all potential clients (with sufficient NTFS permissions to
permit reading from the share).

4. After initial deployment (via the e-mail thingie described above), the
application will update itself upon startup.

In other words - we literally don't need to ever touch the existing
desktop image if we go with ClickOnce (or Application Updator) and the app
can be deployed and updated on an ongoing basis automatically. yes?

Am I missing anything or just plain wrong about any of this?

Another option is to run the application from a server. This would require a
shortcut and the change in .Net security for the Intranet zone.

SP

 

[Jordan S.]

RE:
<< Another option is to run the application from a server. >>

Can you please elaborate a bit? This can be accomlished any number of ways
(e.g., via Terminal Services). To which of these are you referring?

 

[SP]

RE:
<< Another option is to run the application from a server. >>

Can you please elaborate a bit? This can be accomlished any number of ways
(e.g., via Terminal Services). To which of these are you referring?

If it is a multi-user LAN application then there is no difference between
the C drive or a network drive with a .Net application except the security
needs to be changed for the Intranet zone. Even in instances where I have a
WAN deployment I still have all the users start with a network based
executable and then I handle the deployment to their local drive for
updates. I am just suggesting these as alternatives to the click once
scenario or local deployment via whatever mechanism they have in place.

SP