WinApp Deployment

[a]

Hello All,

I am frustrated with the concept of No-Touch Deployment. This was a big
marketing aspect of the .NET development model, but there are many ways to
do it, and none of them are working for me. The Updater Application Block
requires BITS, its own service, a script file, etc. This is a deployment
issue to begin with. The 'navigate to an '.exe' file doesn't seem to work
on my W2K3 Server, through an ISA firewall. (no idea where the issue is,
just nothing happens when I navigate to the URL from my network. It works on
the server itself. The server is in my Trusted Zone. I don't want to go
opening huge holes without knowing how to approach this). Will W2K3 Server
server the EXE over the net by default? Is my ISA Server preventing it?

When I do run it on the server itself, I then get security issues related to
the fact that my app hits a web service. Is this an effective means of
deploying an application that will need to hit the user's hard drive, as
well as a database / web service? How would I go about implementing it?
Or, am I better to use the Updater Application Block? I have not found any
article that details the security side of this, How To, Best Practices, etc.
Just a few articles that make it sound so simple.

Kevin

 

[Scot Rose [MSFT]]

Have you looked at the Deploying .NET Applications Lifecycle Guide?

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/DALGRoadmap.asp


Scot Rose, MCSD
Microsoft Visual Basic Developer Support
Email : (e-mail address removed) <Remove word online. from address>

This posting is provided “AS IS”, with no warranties, and confers no rights.

Get Secure!
http://www.microsoft.com/security
http://www.microsoft.com/protect


--------------------