DEV Community: Jose Antonio Felix

Use async await on c# 🚀 (easy way)

Jose Antonio Felix — Sat, 08 Jan 2022 03:38:47 +0000

Do you want to use async/await on c# ? (yes, as in javascript) Okey, I'll show you how to do that in an easy way 😎

First of all

You should have your project on c# (.net core/framework) created.

Let's start

There are a few concepts that you need to know, so this tutorial is divided into several small sections:

Task class 🧙 your best friend
The task class on c# represents an async operation, this operation can be a simple method wich will be called without interrupt the current process thread, it'll run on another Thread, but you don't have to do any complex syntax, just call a method.

This is the basic usage:

We can see, 3 elements:

The Task class constructor and variable task1
A lambda expression (is like an arrow function): that represent the operation wich we want to run (lambda expression in c#).
Start method call: run the operation asynchronously

Output:

Hello! this will run async

A more detailed example 👀
The task class is a powerful tool of c#, but maybe you got confused on how and when it is running.

Well this is a more detailed example, we have 2 tasks to do:

As you can see, the 2 tasks are example operations wich use Thread.Sleep(miliseconds) function to stop temporaly the task thread (to simulate a real operation).

So, let's Start these tasks and check it's behaviour:

Output

Starting all tasks
Starting task 1
Starting task 2
------------------------------------
All tasks have finished, or not?
Task 1 done
Task 2 done

As we can see, the 2 tasks have been called asynchronously, and it's output is on the bottom.

But what happend with the All tasks have finished, or not? line, it should appear after tasks have been done, how can we do that? It's very easy, and we'll see it on the next section

Async/Await 🪄
Async/Await in c# is simple. You just have to put the async word in a method, example:
public void DoSomething() to public async void DoSomething().

Now, this method is able to "await" a Task until it finishes its work, using the await word before the task name 🤯

So, we can modify the example of the previous section to make it an async method:

As we can see, the code is inside of an async method called Main. Also, we add await task, this will allow us to control the code flow.

Now, the task 1 will start with task1.Start() normally, but the await task1 statement won't allow the code execution to continue until the task 1 has finished. The same behaviour for the task 2.

The output:

Starting all tasks

Hello! this will run async
Starting task 1
Task 1 done
Starting task 2
Task 2 done
------------------------------------
All tasks have finished, or not?

We have fixed the problems we saw in the previous section.

The line All tasks have finished, or not? is at the end
Also, both tasks run as a synchronous operation, but with the advantages of Async/Await features 💪

The Async/Await and Task class are powerful tools to make concurrent, efficient and legible code without much effort 🚀.

There are more useful uses of these features, you can leave me a comment if you want more tutorials about C# or something else 👀

Learn Github && Git in an afternoon (Beginners) 🐱‍💻☁️

Jose Antonio Felix — Tue, 09 Nov 2021 00:40:01 +0000

If you want to have your code available in a cloud git repository (for free) and be able to collaborate with other developers, this tutorial is for you 😎💻. Firstly, we have to know some concepts:

Git
If you don't know Git (in basic terms), you need to see the post attached bellow before start this tutorial 👇🏻

Learn Git in an afternoon (Beginners) 😎🐱‍💻

Jose Antonio Felix ・ Oct 27 '21

#github #git #beginners #code
Github

Github

Is a platform where you can put your code in a cloud git repository completely free and where other developers could see your code and contribute or use it.

Github is very useful and is used by a lot of developers in the world. This tool could allow you to improve as developer and be atractive to software companies.

First of all

We'll learn the Github (and some Git) basics in this tutorial, if you already know Git fundamentals (repository, commits, log, etc) you're fine, but if you don't, please check the post attached on the previous "Git" tab. Good luck!🤠

How to use Github

First, we have few things that we should have/know:
Pre-requisites

A Github account. Create one here
Git installed on your PC. Learn Git
Follow me on Github 🐱‍🏍🎯

Now we can start the tutorial properly, next we'll see some sections where we will:

Create a Github repository ☁️🐱‍👓
When you're in the Github main page (logged), you'll see this button:

Click on it and you'll see this page:

This page is very intuitive, but I'll explain the elements on it:

Repository name: Is the name wich the people will see in your repositories list, find a cool and explicative one.
Description: Here you'll explain the project in a few words. Maybe you could write the objective or the tech used on it.
Public/Private: If you want to show your repo to other developers, set public (recommended). If you want to keep the project only for you, set private.

The following 3 options can be skipped for now, we just have to click on create repository button:

Now, We have done our repository successfully, we'll see something like this:

Don't worry if you don't understand what that is, we'll see about it in the next steps. For now, you just need to know that you have your first Github repository! 🐱‍👓

Configure and push your local repository 🧪
We already have our Github repository, but also we need a local Git repository on our pc. If you don't know how to create one, you need to see this post.

Okay, the following is an example local repository with 3 files and few commits:

We have to upload or push our local repository to the Github repository, is like sync both. For this we have to do the following:

Do you remember the github page of our new repository? there we found this commands:

git remote add origin URL_EXAMPLE
This git command allow you to add a new remote repository (URL) to your local repository, that means that you could upload your commits (push), update your local repository (pull) and more.

In this case, we're adding a new remote URL_EXAMPLE with the alias origin.

git branch -M main
This command change the branch name of our repository to "main". The reason of the change is because by default git names the branch "master" and Github need a branch named "main" (to avoid racial discrimination of master and slave).
The branch concept needs a more complete explanation to be understood, but for now isn't necesary, just see it like the main name of this repository.

git push -u origin main
This is the interesting thing.

The git push command allow us to push (upload) our commits to the github repo.
The origin main indicates that we want to push the changes to the remote named "origin" (setted on the first command) and the branch named "main" (setted on the previous command)
The -u is an option to set the origin main options to default on the future git push/pulls calls.

Now we know what this commands are for, so we can type them on the terminal an check the results:

(When you enter the last command a window will open and it will ask you to login to Github, just enter your account and password and continue. This will happen only 1 time)

If you refresh the repository page, you'll see your files and you could check interesting info like the commits made, the languages used on the repo and it's description.

Finally, we'll have our repository on Github! And the best part is comming! In the next sections you'll learn what things you can do with Git and Github.

Push new commits 🚀
In the last section we have pushed our local repository to the Github. Now, both repositories have the same commits. But maybe we want to make more local changes and then commit and push it to the Github repo again. Okay, Let's do it.

First, we'll make some changes:

Then, add the changes and commit it:

Now, we can get the repository log (history) to see the new commit:

As we can see, the new commit was made successfully. But this commit is only in the local repository, and it need to be pushed to the Github repo.

For this, we can type one of the following commands:
git push
or
git push origin main

Both work fine, the difference is that the second one declare explicitly in wich "remote" and "branch" the commits will be pushed. And the first one just take the default settings.

(If you rememeber, this "remote" and "branch" default settings was been setted in the previous section on the git push -u origin main command, thanks to the -u option) 🤯

When we enter one of this commands, we'll get:

Now, if we go to the Github repository page again and refresh it, we'll see our new commit(s) 😎.

Clone a repository 🐑
In the last sections, we have created new repositories and push our local commits to github, but, if we want to download a Github repository to our local computer, what do we have to do? Well, this process is called "cloning".

To clone a repository we have to know some things:

We need the real URL of the repository wich we want to clone. For get it, we have to go to the github repository page and copy this:
We can clone whatever public repository that we want, this means that we can go to the page of any repository of any user and copy it's link and clone it on our pc, this is awesome 🤩 because we are able to download every open source code , for example we can go to the oficial Microsoft Visual Studio code repository, clone it, change it's code and modify it as we want 🧨

For this example, we'll clone this Example repository. So, go and copy it's URL.

Now, we have to open a terminal and go to the folder where we want to clone the repo:

In my case, I want to clone it in D:\personal-projects> folder.

Now we just have to type this command:
git clone https://github.com/JAFB321/devto-learn-github.git

We'll get something like this:

This should have created a new folder called like the repository cloned. In this case, the folder is D:\personal-projects\devto-learn-github.

Then this folder will have all repository files:

Now we can open a terminal on this folder and type git log --oneline or git status to check the new local repository:

Now we can make changes and commit them as we want. But, can we push this new commits to the original Github repo? 🤔 In this case, you won't be able to do that, Why?🤨 because the repository isn't yours, you don't have permission to push changes to repositories that you aren't the owner (or where you don't have explicit access).

For get permission and do that, we have 2 options:

Request write access to a Github repository to the owner.
Make a copy of the Github project on your own Github repositories or Fork a project.

Both options are material for another tutorial, we won't see them in this one.

Obviously, if you clone a repository wich you're the owner (like the repo that you created on the first sections) you are able to push your changes to the Github repo without problem.

Update local repo with last changes 🔁
Imagine you have a Github repo, and you clone it on you laptop 💻 and your desktop pc 🖥️. You go to the laptop and do some changes and make a couple of committs, then you push that commits to the Github repo. Now, you have 1 local repository outdated (in your desktop pc).

To update the desktop pc repository, you must pull the new changes from the Github repo.

How to solve the problem

To do that, we'll clone one of our Github repo 2 times in our pc.
We'll create 2 folders to clone the repo 1 time on each folder:

We have 2 copies of the same Github repository on our pc. I cloned my own repository but you must clone one of your own Github repos (for example the repo you created in first sections).

Now, we'll make some new commits on the example-repo1:

And push them:

Note that you don't need to type -u origin main because is a cloned repository, and these options were set in the cloning process automaticaly.

Once this is done, we have the Github repository and example-repo1 updated, but example-repo2 is outdated because it doesn't have the 2 last commits.

To update example-repo2 we need to pull this new commits from Github repo. For that we have to type one of the following commands on the terminal in example-repo2 repo:

git pull
or
git pull origin main

Both work fine, the difference is the same of the git push command where origin main are the "remote" and "branch" explicity defined.

When we enter one of these comands, we'll get:

The elements inside blue rectangle are the changes summary of the commits downloaded. If we run git log --oneline we'll see these new commits:

Now we have the 2 repositories updated and ready to work 😎. But take care about pull and push your commits on 2+ copies of the same cloned repository, because if you make different local commits on each repo separately and try to push them at same time you could get a merge error 🌪️, but don't worry there is an easy solution for those kinds of problems wich we'll see on future Git tutorials 🐱‍🏍.

There are a lot of useful and interesting things that you can do with Git + Github, in this tutorial you have learned the most important topics 🥇.

You have learned a lot but there are still more things to learn wich can help you to be a very efficient developer, contribute to the open source community and grow in the IT world 🤖.

(If you want to understand the meme, don't forget follow me to learn about git branches, merge, fork and more 🎈)

Learn Git in an afternoon (Beginners) 😎🐱‍💻

Jose Antonio Felix — Wed, 27 Oct 2021 02:33:26 +0000

Do you want to be able to have the control of your code and have a trustworthy and easy to make history of it?📚 If yes, this quick tutorial is for you!. First of all, we have to know some concepts:

Git

Acording to Git scm. Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Git is easy to learn and has a tiny footprint with lightning fast performance.

Github

Is a platform where you can put your code in a cloud git repository completely free and where other developers could see your code and contribute or use it.

Github is very useful and is used by a lot of developers in the world. This tool could allow you to improve as developer and be atractive to software companies.

We won't learn about Github in this tutorial, but if you want to learn it, check this:

Learn Github && Git in an afternoon (Beginners) 🐱‍💻☁️

Jose Antonio Felix ・ Nov 9 '21

#github #git #beginners #code

How to install Git

First of all, we need to download Git and install it in our pc 💻. The install process is easy, you only need to open the installer and leave default options (if you want), then click next, next, install up to finish the installation

How to use Git

Git doesn't has a graphic user interface, so we have to use the terminal (cmd, powershell, bash, etc). Don't worry, the use of git is very intuitive and colorfuly ✨.

Here are the basics about Git, I'll try to explain each one in the easier way possible

Create a repository 🛠
First thing that you need to do, is create a repository, for this you have to open your terminal and find/create the folder where your project is.

Now, we have to type in the terminal this:

git init

You'll get something like this:

And the job is done! we have our git repository initialized 💪🏻, Go to the later steps.

Add your files to the repository 🛒

In Git, you have to specify what files will be added on your repository. To know what files can be added you can type:

git status

And get something like this:

The command shows the status of all project files, In this case the red ones are untracked files, that means these files will be ignored by git, unless we add them to the repository, for this, we can type:
git add app.js
and
git add index.html

useful tip 🤓
There is a way to add all untracked/modified files to the repo. in one line, you just have to type a dot instead of the file name:
git add .

Now, we have our files added to the project, so if we run a git status again we'll have:

But, what does mean this? Well, as we can see, the green color filenames with "new file:" tag indicates that these files have been added succesfully to the repo.
So, we can start to use these files and make our history of changes and other interesting things.
For that, continue with the next step 👇🏻.

Commit our changes 🧪
In the last step, we added the files to the repository. When we add some file, the file is handled by git, but it isn't part of the history of changes, for this we need to "commit" our changes.

For commit the pending changes (in this case, the added files), we can type a command like the following:
git commit -m "Initial files"

In this command, the structure is the following:

git commit : Indicates that you'll commit the pending changes (all green files getted on "git status" will be committed).
-m "Initial files" : These are optional, but is strongly recommended put it because the text between quotes is the message, and servers to set the reason/sense/description of the commit. Good commit descriptions allows you (and others) understand better your code 🤔. This commit message should have the what? and why? of your code changes.

We type "Inital files" because we are adding the app.js and index.html for first time, and its are the first files in our project.

After entering that last command we'll get:
(When you enter this command first time, git will ask you for an username and email, this is for author register only)

Now, if we type again git status, we'll get:

That means we have done the commit successfully and the repository doesn't have pending changes.

Now, since we have made our first commit, it means that we can see it in the repository history, for this we just have to type:
git log

There, you could see all commits made in this repository (we'll see git log command more detailed in the other step).

Now, we'll modify the file app.js

If we modify some file, git will detect the changes automatically (the file must have been added with git add before).

Now, we can type git status again to see the changes:

The important thing here, is the red label modified: app.js. The difference between this result and the first git status is the "modified:" instead of "new:" tag.

This is beacause we have already added and commited the app.js file for first time, but now we have made modifications, then we need to add and commit again this changed file 👇🏼

Now we can commit this new change typing:


git add app.js
git commit -m "change welcome text"


git commit app.js -m "change welcome text"

Both work fine, but if you want to add more files in one commit you should use git add way.

Now, we can type git log again to see the new history:

In the next step, we'll see more details about git log command, it will be a short section.

Repository history 📚
Here, we'll see some tips for git log command, and I'll try to explain a couple of important things about it.

git log structure:

Red mark: Commit ID

This is auto-generated for git and identify a specific commit

Yellow mark: Commit message

Is the text wich we putted in git commit -m "message"

Blue mark: HEAD -> branch

This can sound confusing, but indicates in wich "branch" of the repo we are, don't worry, you don't need to know this for now, will be nice in the future, but not for the basics 🤠

Useful Tip 💡:
You can type git log --oneline and you'll get a better and more readable output of your commit history:

Now we have a more simple log, (note that ID is reduced to it's 7 last characters).

There are a lot of other interesting things that you can do with git, but this tutorial is more focused on the basics, so feel free to practice and learning more about it!

I'll write more useful posts about Git, Github and stuff. So follow me if you want to learn 📌

(If you want to understand the meme, don't forget follow me to learn about git branches, gitignore, merge, remote, github, etc 🎈)

How to expose LocalHost to internet ? Easy way 📶

Jose Antonio Felix — Sat, 23 Oct 2021 07:31:52 +0000

Have you ever wanted to show to your friends your awesome web page, API, etc. But you found that this project is running on localhost? 🤔

Well, there is a way to expose this localhost to the internet and get an https URL easy and for free 😎

For this we can use this app:

Ngrok

Ngrok give you the ability to expose a specific port of your localhost and share an http/https URL to your friends.

How to use

1.- Download Ngrok here and open it

2.- When you open first time the ngrok.exe it will be installed automaticaly, for use it you have to open a command prompt and type:
ngrok http PORT

in example, if we want to expose a web page and its server is running on port 8080, we will type:
ngrok http 8080

So when we run this command, we will get this:

That means we can copy this new URL and paste it on our browser and we could access to our page/api/etc from every pc, as if we were on localhost 😎.

We'll have 2 hours to expose our localhost, but don't worry, when this time get's over, we can re-run ngrok command and it will work again!!

If you liked this tutorial like it and follow me if you want! Thank you for reading

DEV Community: Jose Antonio Felix

Use async await on c# 🚀 (easy way)

First of all

Let's start

More Git tutorials? Whats next...

Learn Github && Git in an afternoon (Beginners) 🐱‍💻☁️

Learn Git in an afternoon (Beginners) 😎🐱‍💻

Jose Antonio Felix ・ Oct 27 '21

Github

First of all

How to use Github

How to solve the problem

Learn Git in an afternoon (Beginners) 😎🐱‍💻

Git

Github

Learn Github && Git in an afternoon (Beginners) 🐱‍💻☁️

Jose Antonio Felix ・ Nov 9 '21

How to install Git

How to use Git

git log structure:

How to expose LocalHost to internet ? Easy way 📶

Ngrok

How to use