I use FileZilla to securely upload files that are not permitted to be sent via insecure methods like email or web forms. FileZilla is great to test the ability to "reach" the remote SFTP server and to verify my files arrived. Once I have tested that, then our internal IT group automates the uploads to these third parties, however I can always manually log into FIleZilla to verify the uploads.
IIS as a web application server is perfectly suited for .net, .net core, asp.net applications. Our core ESB runs on IIS and has hundreds of gigabytes of data moved through it every day spread across millions of transactions. We have other mission critical applications that deliver our results to patients and doctors relying on IIS web application servers. If you stay in the Microsoft development stack, IIS is a top tier, efficient, and reliable web server.
Easy to use - Some FTP servers bury their functionality in window after window of settings. Not FileZilla. You can get up and running in a few seconds.
Drag and drop - FileZilla allows easy uploading and downloading via drag-and-drop.
Edit in place - FileZilla allows users to edit a text file (or HTML, etc) in place and automatically upload the changes upon save. This is a great feature for making quick edits to a website!
A big advantage that we use all the time is reviewing the logs that automatically get generated in IIS. It has helped us troubleshoot various problems in our applications over the years.
IIS integrates really well with Visual Studio and TFS. We are able to quickly deploy new applications and changes to applications when requested by the business.
IIS has proven that it is easy to configure and maintain with minimal effort.
The editing and viewing feature in FileZilla is not as user-friendly as some other applications. Editing sometimes requires downloading a file and editing it, and then re-applying the file.
Placing and saving encryption keys can sometimes be difficult for non-expert users. FileZilla-driven prompts to assist in this would be helpful.
The cluttered interface sometimes seems non-navigable. There are many times too many windows and unclear where the actual "action" is occurring.
We have no intention to replace all applications running on top of the IIS platform. Not all applications support other platforms and not all support staff are skilled in Linux/Apache platform support. Whereas IIS may not be the best performing or most secure web platform available, for the aforementioned reasons, it is impossible not to continue use of this product.
FileZilla is really easy to understand and makes it easy to log into servers to upload files. Moving files around is a breeze (even if it's a little tedious to wait for large quantities to move one by one) and editing html and css files directly is a feature it would be difficult for us to live without
In general, Microsoft IIS is an alright product. It comes natively with Windows Server. It has good enough GUI to set things up & tweak things around. Once properly setup, it runs stably enough. And with enough Powershell magic, having a CI/CD pipeline to automatically deploy a new version of the application is doable.
ARR (application request routing) in Microsoft IIS Server enables the web-admins to increase the web app reliability and availability through the rule based routing and load balancing of HTTP requests which in turn provides highly available server. IIS 7.0 Manager also provides kernel as well as user mode caching for faster performance and in case if the server fails, the IIS server has good amount of details logged in its log files which help understand and debug the cause quickly. Load balancing facilitates IIS server to fight against availability issues.
In my experience, I have never had significant issues with IIS performance. Sometimes I've experienced issues with loading time, but it is mostly related to the web site code. However Amazon, Microsoft and Google providing free cloud services with very limited resources, and in that scenario, "heavy" websites on IIS could be the issue. In other situations - performance is good.
I've always found the setup of FileZilla to be easy to use and setting up new sites has been quick. In working with FileZilla, I haven't had any issues. I rate it high because it's easy, quick, and free. I think anyone that is familiar with File Explorer can use FileZilla.
As mentioned earlier there is so much documentation or guides or stack overflow questions out there that someone will have faced the same or very similar scenario to what you are going through that you will almost certainly find a solution to what you are after.
Well, we sent an email to the organization 10 days ago and have yet to receive a response. The email had to be sent because their systems do not recognize the purchase yet when we made it we found the information they were using was false. Thus, we file a complaint with our payment processor and asked for our money to be refunded. That process generates several emails from the FileZilla organization asking that we reconsider as well as changing our rating of their services. We did do that AFTER they gave us the correct credentials to be able to download the product. However, when we did everything we were supposed to do to get registered with the User Community, we got several error messages stating that the purchase was not recognized as being valid and they had no record that we made a purchase thus deny entry into their User Community. We are at the current opinion that it is no longer the same organization it was years ago like they really don't care about the product. We've also been having, from time to time, transfer errors popping up within the Free product for which you have very old reviews.
On Windows, Microsoft IIS is easier to implement and maintain than Apache web service. Normally if you need to host PHP or other apache native content on a Windows server, it's recommended to use WAMP or equivalent software to simplify the installation, administration, and configuration of resources. However, you can use Microsoft IIS and other web services on the same server, taking care to keep separate folders and port usage for each system.
Microsoft IIS Server is scalable if the underlying server configuration is done correctly. Use x64 edition v/s 32bit and using 32bit mode application pools are some of the tweaks to be done to make the IIS server scalable. There are too many small configurations need to be carried out in order to make a highly scalable IIS server hence not giving full score in this area.
Speed of development. You don't need to be an expert to expose your website through some DNS
Robust, there has never been any downtime because of IIS itself.
The ease of use can have (and has had) some negative impact because it's too easy to implement something, and then forget. When a server is taken down, those unthoughtful implementations come to light the hard way.
