All geek questions in one place

Publish ASP.NET and copy files

I want to know for sure if there are any possible problems for publishing an ASP.NET solution.

In my current policy of my company (oddly enough) they just copy the dll of the web project and need the dlls, web.config and global.ASAX links and image files on top of the existing ones on the IIS web server (a virtual directory is created).

Do you see any problems with the above?

Your feedback is greatly appreciated.

+4
source share
2 answers

I do not see a problem with this. This is what we do. We publish in a folder - any folder, check web.config for live, and then zip it. Then we create a change request by referencing the zip file and pass it on to the hosting team for deployment.

This works great for us, but then everyone has different views and circumstances. I do not see this as a technical problem, but more of a business process problem.

+3
source

It used to be that you didn’t copy files enough, because you need to create a virtual directory / Application in the IIS configuration system for your applications. Recent versions of IIS allow you to fully handle this in app.config, and therefore this is a much less problem.

+1
source

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

More articles:


All Articles