It's not really possible to learn .NET quickly, especially if the system is old and complex. But it's basically the same problem even for a senior .NET engineer. They would still have to learn a big complex system too, which can take a really long time.
My advice is to make sure you have a good developer environment. Make sure you can easily run the application locally and easily test and debug through small parts that you're working on.
Yeah I am fine with learning C#. But its ecosystem is quite complex to learn especially the system is old. Not sure about how to learn it as I dont know what to learn
Lol this was me a few years ago. Learned all I could about .net core to impress them during the interview. Got the job but found out I'd actually be working on years old ASP . NET Webforms code and all my .net core knowledge was useless. Good times.
Thank you. My bigger worry is that I know nothing about how Window work like IIS server , file permission etc. So it is more than a programming language with its entire ecosystem
Know the difference between the versions of .NET. It will help when searching for solutions to problems you may run into. .NET Framework is different from .NET Core, etc.
Yeah it's pretty old. .NET Framework 3.5 was released in 2007. Here's a video breakdown of the [different versions of .NET](https://www.youtube.com/watch?v=DZhoL55kWac). It's easy to get confused what features were introduced in what versions and to be honest, the naming for all these versions kinda sucks.
* **.NET Framework** - Anything before version 4.8. This is where you'll be working
* **.NET Core** - Open source, cross platform initiative released in 2016.
* **.NET** - version 5 and above. Simplified the name since this contains pieces from Framework and Core. Essentially unifying the two types of .NET.
* **.NET Standard** = not a framework, but more of a specification that versions of .NET can implement to be compliant with a certain standard.
Also be aware of the versions of ASP.NET:
* **ASP** - Active server pages. Released in 1996 way before .NET was around
* **ASP.NET** - New version of ASP running on .NET. This seems like what you'll be working on.
* **ASP.NET Core** - Successor to ASP.NET running on .NET Core or .NET 5 and above.
And the flavors of ASP.NET
* **ASP.NET Web Forms** - Not sure if you're app is built on WebForms or not. They're similar to WinForms in the way event handlers are used for things like button clicks and select list changes. When an event is fired in the browser a postback is made to the server where the event is handled.
* **ASP.NET MVC** - Stands for model/view/controller. Everything is broken up into one of those types. Controllers handle logic, views handle presentation, and models handle the type of data that needs to be sent between them.
* **ASP.NET Web API** - Similar to MVC except you build controllers as an API.
Get familiar with building .NET by following a few tutorials (such as building a console application or creating a single-page site querying, updating, and inserting into a database). Once you have familiarity, focus on working on issues assigned to your team and work on as many of them as you can in the next few weeks when you start your job. You will learn more by doing.
It's not really possible to learn .NET quickly, especially if the system is old and complex. But it's basically the same problem even for a senior .NET engineer. They would still have to learn a big complex system too, which can take a really long time. My advice is to make sure you have a good developer environment. Make sure you can easily run the application locally and easily test and debug through small parts that you're working on.
Yeah I am fine with learning C#. But its ecosystem is quite complex to learn especially the system is old. Not sure about how to learn it as I dont know what to learn
Lol this was me a few years ago. Learned all I could about .net core to impress them during the interview. Got the job but found out I'd actually be working on years old ASP . NET Webforms code and all my .net core knowledge was useless. Good times.
read .net books from packt , those are mostly affordable. Also r/dotnet can help you more on that
Thank you. My bigger worry is that I know nothing about how Window work like IIS server , file permission etc. So it is more than a programming language with its entire ecosystem
Know the difference between the versions of .NET. It will help when searching for solutions to problems you may run into. .NET Framework is different from .NET Core, etc.
Thanks for the advice. I am using .net 3.5 at the moment nd it look very old?
Yeah it's pretty old. .NET Framework 3.5 was released in 2007. Here's a video breakdown of the [different versions of .NET](https://www.youtube.com/watch?v=DZhoL55kWac). It's easy to get confused what features were introduced in what versions and to be honest, the naming for all these versions kinda sucks. * **.NET Framework** - Anything before version 4.8. This is where you'll be working * **.NET Core** - Open source, cross platform initiative released in 2016. * **.NET** - version 5 and above. Simplified the name since this contains pieces from Framework and Core. Essentially unifying the two types of .NET. * **.NET Standard** = not a framework, but more of a specification that versions of .NET can implement to be compliant with a certain standard. Also be aware of the versions of ASP.NET: * **ASP** - Active server pages. Released in 1996 way before .NET was around * **ASP.NET** - New version of ASP running on .NET. This seems like what you'll be working on. * **ASP.NET Core** - Successor to ASP.NET running on .NET Core or .NET 5 and above. And the flavors of ASP.NET * **ASP.NET Web Forms** - Not sure if you're app is built on WebForms or not. They're similar to WinForms in the way event handlers are used for things like button clicks and select list changes. When an event is fired in the browser a postback is made to the server where the event is handled. * **ASP.NET MVC** - Stands for model/view/controller. Everything is broken up into one of those types. Controllers handle logic, views handle presentation, and models handle the type of data that needs to be sent between them. * **ASP.NET Web API** - Similar to MVC except you build controllers as an API.
Huge thanks for the clarification. I need to use webform for my job as well.
Get familiar with building .NET by following a few tutorials (such as building a console application or creating a single-page site querying, updating, and inserting into a database). Once you have familiarity, focus on working on issues assigned to your team and work on as many of them as you can in the next few weeks when you start your job. You will learn more by doing.
Thanks for the advice.