Gustav Brock
Gustav at cactus.dk
Wed Apr 1 16:17:01 CDT 2009
Hi Shamil Indeed! Highly recommended: http://databaseadvisors.com/pipermail/dba-vb/2008-October/002037.html I have installed a web server (IIS) at the client to which I have external access and publish the app to this directly from VS (via FTP) when a revision has been made. It can't be easier. /gustav PS: Will return to the SCRUM stuff tomorrow. It's bedtime here ... >>> Salakhetdinov Shamil <mcp2004 at mail.ru> 01-04-2009 21:14 >>> Hi All, Does anybody have .NET Apps Click-Once setup experience - namely .NET WPF apps Click-Once experience? I wonder how much time it could be needed for me to configure and test such setup assuming I have WPF appricaltion ready? My customer also wanted to have CompanyName and UserId specified and somehow passed from Click-Once URL http://my-click-once-application-url?c=company&u=userid to the local application when it is installed first time/updated/on-start-up to get UserId in login dialog - is it possible to get such params somehow by the subject application passed to the latter "automagically" in e.g. standard start-up arguments or something like that? Thank you. -- Shamil P.S. "WPF App deployed with ClickOnce": http://stackoverflow.com/questions/461186/is-this-list-a-correct-understanding-of-microsofts-current-application-deploymen requires two clicks (click hyperlink, click yes), no user input only for current user, no per-machine installations no shortcuts on desktop appears in program list like normal applications applications files are always copied to ../My Documents/My Applications a shortcut to your application will be put in Start menu / your company name cannot modify the target computer, isolated from operating system automatically detects and updates a newer version published simply by putting them on a webserver (where clients detect and get them) requires .NET 2.0 or later comparable to Java Web Start solves four problems: (1) easy deployment, (2) easy updating, (3) low-impact on target computer, (4) no need for administrator permissions. considered "low impact" if two users have the same ClickOnce applciation installed on the same machine, they will not break each other employs CAS for security user does not have to be online to use application standalone ClickOnce apps do not work on Firefox and Mac with Firefox now since it needs the .NET runtime restricted to single-window apps since they run in the browser building a ClickOnce manifest is much easier than Silverlight etc, since the IDE will do almost all of it for you; you just have to host the files somewhere (could be a web URL; could be a network UNC).