All geek questions in one place

Deploying ASP.NET Applications: Push vs. Pull

How do you deploy ASP.NET applications? Do you push it to production servers using UNC paths / mapped drives? FTP? SFTP? SSH / SCP (via a third-party application installed)? Something other? Or are you pulling it from production servers using a version control update or other mechanism? Consider production servers located on the Internet or in the DMZ, push requires opening insecure firewall ports (for UNC or FTP), right?

I am trying to reinforce my deployment philosophy for ASP.NET. The pieces that my ideal one-click build / deployment process will include include: MSBuild, Web Deployment Projects, CruiseControl.NET. But I'm still struggling with how to actually deliver the bit to the production server.

After spending time on the Windows and * nix platforms, I am disappointed in the history of Windows deployment, so I wonder how others do it.

+3
source share
2 answers

I use cruisecontrol.net and am very pleased with this. I have a nant script that calls cruise control, which:

  • Gets a source from our intermediate SVN branch
  • Creates it
  • Copy files to each production server
  • svn, , .

! , , . script. , .

+2

:

  • Visual Studio
  • (, -, ...)
  • Zip
  • temp ( )
  • ,
  • script ( ), .

( , , (?) , script . , , , .)

+2

Source: https://habr.com/ru/post/1717965/

More articles:


All Articles