omg, thank you so much. I be creating so many projectfiles cuz I didn't figure out how to debug other projects I create in a single file. you a lifesaver :)
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.
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.
Could I ask a question about " How do I deploy multiple projects in same solution " Because we have 4 projects in a single Solution and its can call each other Project's Form after publishing.
It depends. If each project is an actual application, they’ll have to expose means to allow for communication between each other, for example, when web APIs expose endpoints for HTTP calls. If you have class libraries, they’ll be included as DLL’s when you publish the main application.
Is Possible if i using Multiple Platform Target (X64) - (X86) in one project.? Cause i have a problem with this, cause my FormA has X86 - and i must to develop a new Form within the references is X64.. Thanks Man..
If you're using .NET Core (or .NET 5), at publish time you can configure the target platform. The same project can be published in a variety of platforms, in that case.
It does affect the end result, as these are two very different types of application. If you need a GUI, I’d just recreate the project and bring over the code.
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
Was disappointed. Need information on how to manage cases where multiple projects are dependent on each other for the build. If you set the Dependancies on the project, Say you have projectA,B,C in the solution and C requires B be built and B requires A be built. By setting the Dependancies this will allow a "Rebuild Solution" to sequence the build correctly. Say, for example you run a "Rebuild Solution" in this case which builds everything. Then you change JUST project "C" and want to just build those changes. With the build dependancies set, it is unable (for some reason) to detect that project A & B did not require building and builds A, then B, before building C. So there is no build time savings. If you remove the dependancies, Build works fine, but rebuild all will launch parallel simultaneous builds of A+B+C. I need to understand how to correct the build dependancies so that a "Build" solution or Build of just "C" does not trigger building A & B. Only on a "Rebuild Solution" do I want all projects A,B,C built. So I'm looking for breadcrumbs on that solution.
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.
omg ur my actual hero i had this problem when i made like 2 programs and only the 1 one would start
omg, thank you so much. I be creating so many projectfiles cuz I didn't figure out how to debug other projects I create in a single file. you a lifesaver :)
As others have commented. Thank you! This was surprisingly difficult to find information about. Thanks again, cheers!
Glad it helped!
THANK BRO STILL KILLING IT 2022 MATE THX BRO
You're welcome!
thanks man you resolved my life bruh
Luiz, Thanks for this video. Nice job. Clear, and Consise answer to the problem.
Thank you, Charles!
This is very helpful. Thanks Luiz!
Glad it was helpful!
Thank you very much bro, you helped me so much.
bro ur a lifesaver
Glad it helped!
Thank you man really appreciated :D :D :D
Glad I could help!
How do you publish/ build this entire solution? Seems c# projects can only be built, while asp projects get published.
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.
Very nice! Thank you kind sir!
Glad it was helpful!
Thanks
This helped me so much. Thank you
Glad it helped!
How do we have one project call a method from another 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.
Big Thanks to you 😊
Most welcome 😊
Could I ask a question about " How do I deploy multiple projects in same solution "
Because we have 4 projects in a single Solution and its can call each other Project's Form after publishing.
It depends. If each project is an actual application, they’ll have to expose means to allow for communication between each other, for example, when web APIs expose endpoints for HTTP calls. If you have class libraries, they’ll be included as DLL’s when you publish the main application.
Is Possible if i using Multiple Platform Target (X64) - (X86) in one project.?
Cause i have a problem with this, cause my FormA has X86 - and i must to develop a new Form within the references is X64..
Thanks Man..
If you're using .NET Core (or .NET 5), at publish time you can configure the target platform. The same project can be published in a variety of platforms, in that case.
dont have such an options like set project,
Make sure you’re opening a VS solution (.sln file), and select option “Set as startup project”.
I am making a POS system and instead of adding windows form I accidentally used console application, does it affect the system? Or what should I do?
It does affect the end result, as these are two very different types of application. If you need a GUI, I’d just recreate the project and bring over the code.
Thank you bro)
Happy to help!
and how can i run a .c file whic is independent and without a project>?
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
Thank you bro you are life saver❤
Happy to help!
Thanks bro
Any time
I want to start socket client server, the client is ARM remoted raspberry pi and the server is windows. Is it possible to do this?
I know there is a lot of people using .NET in IoT. I'm sure there is something you can look into for Raspberry Pi!
Thankuuu ❤️
Thank you!
You're welcome!
Thanks so fuckin much
Thank you for watching!
SUSCRIBED ASFK 2022
tnx
:)
Was disappointed. Need information on how to manage cases where multiple projects are dependent on each other for the build.
If you set the Dependancies on the project, Say you have projectA,B,C in the solution and C requires B be built and B requires A be built.
By setting the Dependancies this will allow a "Rebuild Solution" to sequence the build correctly.
Say, for example you run a "Rebuild Solution" in this case which builds everything. Then you change JUST project "C" and want to just build those changes.
With the build dependancies set, it is unable (for some reason) to detect that project A & B did not require building and builds A, then B, before building C.
So there is no build time savings.
If you remove the dependancies, Build works fine, but rebuild all will launch parallel simultaneous builds of A+B+C. I need to understand how to correct the build dependancies so that a "Build" solution or Build of just "C" does not trigger building A & B. Only on a "Rebuild Solution" do I want all projects A,B,C built.
So I'm looking for breadcrumbs on that solution.
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.