You’d probably be working more with the files in the /View folder of their MVC project. And your colleagues will probably be working more in the Model and Controller folders.
The View folder is pretty much HTML (but with a .cshtml file extension), so anything you know like HTML, CSS, JS, Frameworks, Bootstrap, Angular, etc… all still apply and will work here.
The only difference is the Controller will be passing to you Classes/Models to your View page, so you can display them on screen, or send data back to the Controller. So you’ll be primarily working with WebRazor syntax. It’s the way to access the members/elements of your class models.
BTW… everything in C# is a CLASS!
So in a way, it’s kinda similar to embedding variables back in Classic ASP
<h1><%= myTitle %></h2>
which is kinda similar with PHP. And also similar with Rails
<%= @myTitle %>
You need to learn Visual Studio because VS will help you with its Intellisense, code completion and letting you know fixes for common problems. Plus… you need the VS IDE to work with the other aspects of creating a View page, like Partial Views, ViewImports, ViewStart pages, sections, creating ViewModel classes, etc. You’d also need to learn about Html helpers. These helpers “help” you by tying your View to models at the backend. For ex: a typical form may look like
<form asp-action="Edit" method="post">
<td><input asp-for="Title" placeholder="enter movie title" size="30" /></td>
<select asp-for="Genre" asp-items="Html.GetEnumSelectList<Genres>()"></select>
<input type="submit" value="Edit" />
See those asp-* statements? Those will get rendered into proper html later on.
Of course, you can also embed C# code or functions in your Views, use foreach iteration, etc. So that’s when knowledge of C# comes in. The C# syntax is easy to pick up… the challenge is knowing the thousands of C# functions you’ll need to use. But this only comes with experience.
For resources, ASP.NET, the microsoft website, Pluralsight… and some courses on Udemy. – and of course StackOverflow.