Re: Creat an Installation package for client and server

Dave,

Thanks for your response.

I have tried to setup 2 extra setup projects in my application solution. 1
is for client setup and the other is for server setup. As soon as i am done
with this, i have setup.exe and clientsetup.msi under \bin\debug directory
for both client and server. For deployment, i will hand those folder to the
end users and they will run the install. What if i have release a new
version?

About clickonce, it is the great solution for automatically deployment but i
am concern about granting permission when needed. As you mentioned early,
clickonce is not recommended as a public installation. So what is your
recommendation on this? My users are over the state. Thanks,


"Dave Sexton" wrote:

Hi,

Assuming that you have written a client application and a server
application, you should have two separate installation packages unless you
want a fair number of servers to be clients as well.

ClickOnce works quite nicely, but you may have to configure each client to
increase the permission level for your application if it needs FullTrust,
for example. For this reason, it's not recommended as a public installation
method, so you should use a "Setup and Deployment project" instead if you
need higher levels of trust than normally allowed by web installations and
if you don't have access to configure the security levels on each client.

You can create a ClickOnce installation easily in VS 2005, which will also
help to deploy the files to your server. The clients simply need to connect
to your server the first time to install the application and they'll
automatically receive updated software each time a newer version is
available from the server, making maintenance much easier for you and almost
transparent to the end-users.

"ClickOnce Deployment Overview"
http://msdn2.microsoft.com/en-us/library/142dbbz4.aspx

If you are only installing the server software once then you probably won't
need a ClickOnce deployment for that. Just create a "Setup and Deployment"
project in VS 2005.

"Setup and Deployment Projects"
http://msdn2.microsoft.com/en-us/library/wx3b589t(VS.80).aspx

--
Dave Sexton

"piggy" <piggy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C16D6F1A-364B-4538-862F-96B140DA6E80@xxxxxxxxxxxxxxxx
I have developed an application using C# under .NET 2.0 framework. It is
almost done and it is time for me to think about deploymnet to all users.
I
don't have any background about this and would like to see if anyone can
help
me get started. I have read some about clickonce deployment and not sure
much about this yet. Thanks for your help.




.

Relevant Pages

  • 802.1X Setup using Server 03 and Aironet 1200 Series WAP help
    ... I'd really appreciate some direction as I tried to setup a Cisco 1242 ... Series WAP as a Radius Client with 802.1x authentication on a Windows ... Server 2003 R2 DC running IAS/RADIUS,DNS,DHCP. ...
    (microsoft.public.internet.radius)
  • Re: SBS Network Install this weekend - Tips?????
    ... you have to setup the SBS server through CD. ... After the SBS server is ready, then you can start working on clients. ... Before you work on clients, you have to create the client accounts. ... Setup TS in install mode. ...
    (microsoft.public.windows.server.sbs)
  • Re: sbs 2003 fax services
    ... You can try to manually install the shared fax client application on the ... Locate in Client Computers in Server Management console and choose the ... Setup the client computer by running Setup Client Computer wizard to ...
    (microsoft.public.windows.server.sbs)
  • VPN to SBS 2003 Premium behind Netgear FVG318 router
    ... DHCP for all clients and SBS Server ... Setup as DNS, with Exchange running ... VPN to Netgear Router using Netgear VPN Client software working. ...
    (microsoft.public.windows.server.sbs)
  • trouble with shared fax service
    ... I setup the shared fax service for the first time on a machine that has SBS ... Our server has one network card connected to a wireless ... Client problem: After setting up shared fax service on the server, ...
    (microsoft.public.windows.server.sbs)