Using VS to FTP

Question

User-1240188151 posted

Hello,

Two small things:

1) When attempting to use Visual Studio to publish with FTP, it only works properly if we first stop the IIS and THEN publish.  Is there any way to successfully publish without having to stop the server?

2) Also, when publishing a class library, I see it's only possible to publish to a local folder.  Any particular reason for this or easier way of getting up to the server?

Thanks for any help!

Answer 1

User475983607 posted

1) When attempting to use Visual Studio to publish with FTP, it only works properly if we first stop the IIS and THEN publish.  Is there any way to successfully publish without having to stop the server?

You should always stop the application before publishing.  What is the user case for not stopping the web app?

2) Also, when publishing a class library, I see it's only possible to publish to a local folder.  Any particular reason for this or easier way of getting up to the server?

Number 2 does not make sense. A class library is a separate assembly compiled into a DLL and deployed in the bin folder of the web application.  If this is a web site and you are referencing to code in the app_code folder, which is not a class library, then that's just the way a web site works.

Answer 2

User-1240188151 posted

You should always stop the application before publishing.  What is the user case for not stopping the web app?

In this case, we're talking about an intranet site, and I don't want to have to interrupt everybody's work in order to make one small correction in the code.

Answer 3

User475983607 posted

In this case, we're talking about an intranet site, and I don't want to have to interrupt everybody's work in order to make one small correction in the code.

If this is a web site then you might get away with the app not restarting if you deploy an aspx page - can't remember.  IMHO, you should always stop the app before deploying.  Also, depending on what you are dropping on the site, the app might restart anyway so that the new imagine loads.

It sounds like you doing a cowboy deployment and updating a production site whenever you like.  This is a less than optimal deployment strategy and you should consider updating your deployment process.

Answer 4

User-1240188151 posted

It sounds like you doing a cowboy deployment and updating a production site whenever you like.

Cowboy deployment.  I like that! :)

It's true.  The site is being used by 10 people or so.  I'm upgrading from .net to .core.  For .net, I was simply uploading the files, and they would hardly notice the difference.  It made it easier for the bosses to test what they wanted with live information.  Now, we're doing .core, and I'm just putting up a skeleton for them to view.  It's a bit annoying to have to logon to the server and stop the IIS, publish, and restart after every small change.  Whether production or staging.  I thought there would be an easier way.