วีดีโอ

Thanks for your kind words 🙂

Glad it helped!

Make sure you’re opening a VS solution (.sln file), and select option “Set as startup project”.

This is more typical when the project where the method is is a Class Project. Just right-click the “Dependencies” of the project you wanna call the method from, then “Add project reference”. Select the project, and click OK. From there, you can simply reference the namespace where the method owner (class) is wherever you need to call it.

Happy it helped!

Thank you, Charles!

Glad it was helpful!

Glad I could help!

Thanks for your input! This video is intended for absolute beginners (in particular my students), so the scope is limited to the exercise of exploring the very basics around projects and solutions. The scenario you mention is valid, and I may cover it in a future video, but it is not something a beginner would need to worry about when just getting started with Visual Studio.

Yup, both actually mean the same thing. Different books will use different definitions, but the underlying behaviour is identical.

Glad it was helpful!

Glad it was helpful! And thank you for your kind words :)

The terms “build”, “publish”, “release”, and “deploy” are often used interchangeably, but there are nuances to consider depending on context. To keep it simple, let’s say C# projects can do all of these. Now, how a solution is published/released/deployed depends on your solution configuration: 1. You may have a single “main” application that sits alongside other dependency projects in the same solution. In this case, building the main project also builds its dependencies. When deploying/releasing/creating an installer, the dependencies are automatically included. 2. You may have several “whole” applications within the same solution, like different micro-services, a client-side app and a server-side app, a desktop app and a worker service that runs in the background, etc. How to release in this scenario really depends on project types, but generally speaking, the typical solution is to have build/release scripts (which likely build/release projects individually) and/or CI/CD pipelines that integrate with your source control platform and take care of the deployment details.

Glad it helped!

Happy to hear it helped, and thanks for the feedback!

Think of it this way: a static method is usually a “function” that does not represent a behaviour associated with instances of that class. For example, imagine a static method Person.CreatePerson, which returns a Person object. This method would only instantiate the class and return the new instance to the caller. It does not represent something a person can do. Rather, it is more of an utility function (or utility method) associated with the class itself. This method is completely independent of instances, and does not require one to exist in order to be called. On the other hand, a non-static method usually implements the behaviour of an instance. For example, the Person class could define a non-static method Speak. This method is a direct representation of something a person can do, and so its association with an instance (rather than the class) is much stronger. This method requires an instance to exist in order to be called, because it is something a person can do. I have a series of lecture notes where I explain this in more detail. Feel free to check the links below for a more in-depth explanation. luiz.codes/dp?src=%2Fassets%2Fcontent%2Fcsharp%2Fintermediate%2Fmodule-1%2F008-static-and-non-static-methods.txt&hdr=Static%20versus%20Non-Static%20Methods luiz.codes/dp?src=%2Fassets%2Fcontent%2Fcsharp%2Fintermediate%2Fmodule-1%2F009-static-methods.txt&hdr=Static%20Methods luiz.codes/dp?src=%2Fassets%2Fcontent%2Fcsharp%2Fintermediate%2Fmodule-1%2F010-non-static-methods.txt&hdr=Non-Static%20Methods

Glad it was helpful! Thank you for the kind words :)

Glad to hear!

Happy to help!

Happy to help!

Glad it helped!

Thank you 🙂

Any time

Wow, thank you, Sadya!

You can use C++ project templates to write C code with Visual Studio, with some tweaking. learn.microsoft.com/en-us/cpp/build/reference/visual-cpp-project-types?view=msvc-170&viewFallbackFrom=vs-2017

Thanks!

Glad it helped!

Thank you for your feedback! :)

Sorry, what isn’t?

Thank you for watching!

Thanks! 😃

Glad you like them!

Glad to help!

Happy to help!

Glad it helped!

It means the data type cannot change after declaration. In languages like JavaScript, for example, a variable can change types throughout its lifetime. In a strongly-type language like C#, a variable assumes a data type at declaration time, and can only keep values of that type - and the type never changes throughout its lifetime.

Thank you 🙌

You're welcome!

Welcome!

You are very welcome

Glad it was helpful!

Glad it was helpful!

Thank you too!

Thanks for the feedback!