Re: Best Way to Distribute a Winform Application

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Rockford Lhotka (rockyNOSPAM_at_NOSPAMlhotka.net)
Date: 11/12/04

  • Next message: HarlanM: "Foreign key violation on referenced web service dataset" 
    Date: Fri, 12 Nov 2004 11:37:03 -0600

    Assuming all the client workstations on the intranet have network access to
    the SQL server machine, you can use msi, xcopy or no-touch deployment as you
    choose.

    If you have more than around 100 concurrent users, or the client
    workstations can't physically reach the SQL server via the network, then
    you'll need to change your architecture to include an application server.
    Obviously that's more complex, so let's assume it isn't necessary.

    Using msi deployment is a matter of creating an msi using a setup project in
    VS.NET, and putting the msi on a central server so all users have access to
    it. You can link to it from a web page, they can click on the link and
    install the software.

    Using xcopy deployment is a matter of putting the software on a central
    server and having the users copy that directory to their local machine.
    Often this is done with a bat file or a custom app that does the copy.

    Using no-touch deployment is a matter of choosing between a couple options.
    No-touch deployment isn't entirely transparent, and there are two main ways
    to make it work nicely. You can use a launcher app like netrun
    (http://www.lhotka.net/Articles.aspx?id=2f5a8115-b425-4aa1-bae2-b8f80766ecb3),
    or you can use the AppUpdater block
    (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/updater.asp)
    from MSDN.

    NetRun is great if your clients are always connected and you want
    incremental downloads and incremental updates.

    The AppUpdater block is great if you clients might be disconnected, or if
    you want full installs of each version of the software at all times. Note
    that the AppUpdater block is closest to the ClickOnce model coming in VS
    2005, and so it may be a good strategic move in that regard.

    Rocky 

    -- 
Rockford Lhotka
Microsoft Software Legend, Regional Director and MVP
Author of the Expert VB.NET & C# Business Objects books
rocky@lhotka.net    http://www.lhotka.net
"Bob Roggy" <BobRoggy@discussions.microsoft.com> wrote in message 
news:A4DFAE67-4CF1-478D-B889-B76C539CBD90@microsoft.com...
>I have a winform application that accesses a SQL server database. I need to
> deploy it on an intranet. It is an application that will be access by 
> several
> end users. I would like to deploy it in one common place and let end users
> execute the same exe thus making it easy it implement changes as they will 
> be
> needed. How do you deploy a winform application in this manner?
  • Next message: HarlanM: "Foreign key violation on referenced web service dataset"

    Relevant Pages

    • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
      ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
      (microsoft.public.sqlserver.connect)
    • Re: Best way to populate webpages from multiple tables
      ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: Best way to populate webpages from multiple tables
      ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
      (microsoft.public.dotnet.framework.adonet)
    • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
      ... an Access database in former times this was a lot of work which took me ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... client for programming easy, fast and good applications. ...
      (microsoft.public.sqlserver.connect)
    • Re: SQL and Bandwidth use
      ... In addition to the other responses, take a look at the memory and CPU usage ... in Great Plains Client software. ... > near 100Mb/sec bandwidth). ... Client PC is on same segment as SQL server (not passing through ...
      (microsoft.public.sqlserver.server)