
## Table of Contents

- [Introduction](#introduction)
- [Connecting to the FTP Server](#connecting-to-the-ftp-server)
- [Common FTP Commands](#common-ftp-commands)
- [Example: Uploading Files to FTP Server](#example-uploading-files-to-ftp-server)
- [Conclusion](#conclusion)

## Introduction

Here are a few useful tips about connecting to an FTP server by command line.

## Connecting to the FTP Server

> ftp [The server name or IP Address]

> user : [Enter the user name]

> Password: [Enter the password]

After logging in, you can type `help` to see all the commands, or reference the links below to see the details.

ftp command list

## Common FTP Commands

I'll list a few common commands.

`ls` - lists all the files.

```
ftp> ls
```

`dir` - lists files if connected.

```
ftp> dir
```

`get [Host name or IP address]` - connects to the FTP server again.

`mget * or mget *.dll` - gets multiple files by the rule.

```
ftp> mget *
```

`mput * or mput *.dll` - uploads multiple files by rule. `*` means all the files or folders at your current command line directory. `*.dll` means all the files with the `.dll` extension.

```
ftp> mput *
```

`close` - closes the current connection.

```
ftp> close
```

## Example: Uploading Files to FTP Server

Assume the FTP server is set up correctly and you are able to connect with a specific user.

You want to upload all the files and folders from your `E:/test` folder to the FTP server's `DESC` folder.

Open the command line and navigate to `E:/TEST`:

> E:/test

Connect to the FTP server:

> ftp -i [Server name]

Connect with your user and enter the password.

After connecting successfully, navigate to the `DESC` folder:

> cd DESC

When the command line shows `250 CWD Command successful`, you can upload your files to the FTP server folder by typing the following command, which uploads everything from the local command line folder:

> mput \*

## Conclusion

These basic FTP commands allow you to connect to a server, list files, download, and upload files efficiently from the command line. For more advanced operations, refer to the full FTP command reference documentation.


A few useful commands for connecting to an FTP server via the command line.

Few Useful Commands for Connect to FTP


## Table of Contents

- [Introduction](#introduction)
- [Could Not Load File or Assembly](#could-not-load-file-or-assembly)
- [The Solution](#the-solution)
- [Conclusion](#conclusion)

## Introduction

This blog is for when you deploy ASP.NET MVC with NuGet to a Windows server and get an error that assemblies can't be loaded. For example, if you use ASP.NET's bundle feature, which is `System.Web.Optimization`, this blog might help your problem by changing the project reference setting. Basically, you have to change the reference's "Copy Local" property to true.

## Could Not Load File or Assembly

The long story is that after coding your ASP.NET MVC (4 or 5) application, everything works fine on your local machine or local IIS. You also use NuGet as a package manager for your web application, so that during the build, Visual Studio will automatically get the version from nuget.org or other NuGet package providers. My point is everything works fine on your local machine. Now you want to deploy to a web server, assume a Windows server.

So, most of the time it works fine, but sometimes after your deployment, errors appear.

My problem was that my web application used `System.Web.Http`, `System.Web.Http.WebHost`, `System.Web.Optimization`, and `Newtonsoft.Json`. I noticed that I couldn't find any of these inside my web server's bin folder. So, something was wrong with my NuGet setup, or I thought I wasn't doing something correctly.

## The Solution

Should I copy all the NuGet package folders to the web server? When I thought about it, I just needed all the DLLs to be inside the bin folder. Can NuGet do that? I haven't found a way for NuGet to do this directly, but after NuGet adds project references, if the DLL setting's "Copy Local" is set to false, then changing it to true will copy the DLL to the bin folder during the build.

![](https://d1p0mp3f1fx0hz.cloudfront.net/_1d9o29c1o.png)

## Conclusion

When deploying ASP.NET MVC applications that use NuGet packages, ensure that all required assemblies have their "Copy Local" property set to true in the project references. This ensures the DLLs are copied to the bin folder during the build and are available on the web server after deployment.


If you are getting an error such as "Could not load file or assembly" in IIS when deploying ASP.NET, this blog might help you resolve the issue.

WindowsServer

Few Useful Commands for Connect to FTP

Troubleshooting Issue When Deploy ASP.NET MVC5 to Windows Server