Re: Updater Application Block to ClickOnce

Thank you

We need MSI and UAB2 then

Regards, Mark
 

-----Original Message-----
From: Discussion relating to the specifics of the C# and Managed C++
languages [mailto:[email protected]] On Behalf Of Vince P
Sent: Saturday, 19 August 2006 7:21 PM
To: [email protected]
Subject: Re: [DOTNET-CX] Updater Application Block to ClickOnce

The Group Policy Software Deployment and ClickOnce do not "interact".
ClickOnce is strictly a per-user installation mechanism.  The
installation location is deep in the user's local settings file folders.



MSI installs in the Program Files folder.



The twain shall not meet.



The only reason I brought up the fact that you can use both was in the
sense that you can have one group of users having the software installed
via Group Policy (your internal employees, for example), and another
group of folks who install the app via Click Once (remote sales people).



With Group Policy you place the MSI file on a File Share somewhere that
your users have access to and then you configure the policy to install
the app automatically from that location, including subsequent updates.



This is what it looks like:



http://home.comcast.net/~vincep312/GroupMSI.PNG (case sensitive)









-----Original Message-----
From: Discussion relating to the specifics of the C# and Managed C++
languages [mailto:[email protected]] On Behalf Of Mark
Gregory
Sent: Saturday, August 19, 2006 02:54
To: [email protected]
Subject: Re: [DOTNET-CX] Updater Application Block to ClickOnce



Thank you.



So you do an MSI install first to install for all users and put the
files into /program files and you then do updates using ClickOnce after
this?



I would appreciate knowing if this is what your saying.



We need to put the updates on our web server. I think we are halfway
between MSI and clickonce.



Currently we use MSI and UAB2

I'm in the process of going to dotnet 2 and I'm seeing some changes, but
I think we need to stick with MSI and UAB2 possibly for now.



Regards,

Mark





-----Original Message-----

From: Discussion relating to the specifics of the C# and Managed C++
languages [mailto:[email protected]] On Behalf Of Vince P

Sent: Saturday, 19 August 2006 4:38 PM

To: [email protected]

Subject: Re: [DOTNET-CX] Updater Application Block to ClickOnce



If your network is ActiveDirectory , then in my opinion, it sounds like
you should use Group Policy to deploy your applications.



Group Policy deploy has two modes: publish and assign.  You would want
to do an assignment.  Assignment does a pro-active installation of your
application whereas publish requires users to go to Add/Remove Program
and install.



Group Policy works in conjunction with MSI, so you would need to create
a Setup project in Visual Studio for your application and produce a MSI
installation.



Create a policy that points to the MSI and you can target the assignment
to computers and/or users.



Group Policy does understand the concept of application upgrades, so
when you have an updated compilation of your assemblies you add the
updated MSI to Group Policy and link it with the original one.



Here's one source of more info:



 
<http://technet2.microsoft.com/WindowsServer/en/library/5f065962-a6e3-42
2>
http://technet2.microsoft.com/WindowsServer/en/library/5f065962-a6e3-422

a-8d

b7-20a57f40f9f51033.mspx



Note that your app can use both methods of deployment.. ClickOnce and
Group Policy.  The app I made does both.







-----Original Message-----

From: Discussion relating to the specifics of the C# and Managed C++
languages [mailto:[email protected]] On Behalf Of Mark
Gregory

Sent: Friday, August 18, 2006 23:02

To: [email protected]

Subject: Re: [DOTNET-CX] Updater Application Block to ClickOnce



Thank you, it appears - and I may be wrong - that ClickOnce is not the
solution I need due to our needing to install on computers for multiple
users. They are shared computers.



Is this possible with ClickOnce?

Regards

Mark





-----Original Message-----

From: Discussion relating to the specifics of the C# and Managed C++
languages [mailto:[email protected]] On Behalf Of Vince P

Sent: Saturday, 5 August 2006 11:56 PM

To: [email protected]

Subject: Re: [DOTNET-CX] Updater Application Block to ClickOnce



I've used both. From the way I understand ClickOnce there really is
nothing special you have to do to your code in order to enable its
installation/updating functionality.  It's all done externally to the
app.

This would be akin to using the Block to install a stub that installed
the application.



If you made changes inside your app to handle the mechanics of upgrades
then I would guess (though if I were you I would certainty get other
opinions than mine) you wouldn't need it any more.



I've deployed ClickOnce apps over the I-net via IIS server and
internally at my employer using file share and both scenerios are
basically the same steps as each other. Vastly more simple than I
remember the block being.



I would suggest creating a test app, and then going through the VS2005
Documentation, that's all I had as far as resources to learn from and I
managed ok.



---

Vince



> -----Original Message-----

> From: Discussion relating to the specifics of the C# and Managed C++

languages

> [mailto:[email protected]] On Behalf Of Mark Gregory

> Sent: Saturday, August 05, 2006 00:41

> To: [email protected]

> Subject: [DOTNET-CX] Updater Application Block to ClickOnce

>

> Is there a guide on how to go from the Updater Application Block to

ClickOnce?

>

> Regards

> Mark

>

> ===================================

> This list is hosted by DevelopMentor.   <http://www.develop.com>
http://www.develop.com

>

> View archives and manage your subscription(s) at

 <http://discuss.develop.com> http://discuss.develop.com



===================================

This list is hosted by DevelopMentor(r)   <http://www.develop.com>
http://www.develop.com



View archives and manage your subscription(s) at
<http://discuss.develop.com> http://discuss.develop.com



===================================

This list is hosted by DevelopMentor.   <http://www.develop.com>
http://www.develop.com



View archives and manage your subscription(s) at
<http://discuss.develop.com> http://discuss.develop.com



===================================

This list is hosted by DevelopMentor(r)   <http://www.develop.com>
http://www.develop.com



View archives and manage your subscription(s) at
<http://discuss.develop.com> http://discuss.develop.com



===================================

This list is hosted by DevelopMentor.   <http://www.develop.com>
http://www.develop.com



View archives and manage your subscription(s) at
<http://discuss.develop.com> http://discuss.develop.com


===================================
This list is hosted by DevelopMentor(r)  http://www.develop.com

View archives and manage your subscription(s) at
http://discuss.develop.com

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com