How to implement the project .NET (WPF Desktop)?

Good night. At this stage there is a project in Visual Studio, which is the following program:
Window, ribbon, TabControl and StatusBar at the bottom. On the ribbon are buttons that are added to the TabControl tabs, which in turn are UserControl's (implemented in MVVM). Just now there are around 40 UserControl's in the Solution Explorer is already the problem starts with the search of required files (every UserControl is stored in its own folder). In connection with the foregoing had a few questions:
- it is not necessary to rewrite each UserControl in a separate project (.dll) and then drag it into the main window?
- in General, you can read about the correct application architecture (as I understand it, the question for this topic)?
- I would like to start working with your project. Visual Studio Team Services such as appropriate, from where to start learning this service?

Thanks in advance for advice and answers.
July 4th 19 at 23:35
3 answers
July 4th 19 at 23:37
Solution
- it is not necessary to rewrite each UserControl in a separate project (.dll) and then drag it into the main window?

Projects are best done by subsystems or major components in the project, taking into account the existing dependencies. Without seeing your situation it is difficult to recommend a particular solution, but in any case, hardly each control is push in a separate project.

- in General, you can read about the correct application architecture (as I understand it, the question for this topic)?

Raffaele Garofalo, "Building Enterprise Applicatio...

- I would like to start working with your project. Visual Studio Team Services such as appropriate, from where to start learning this service?

It is better to start with Git. It is certainly possible to work with Studio version control, but since you did not work more generally with anything, git would be more versatile skill due to its overwhelming popularity. And Yes, most importantly - you do not need to immediately use some service, the project can be versioned and on the machine and pour in VSTS if necessary. It's amazing how you still did not use any VCS, apparently you are careful and patient man)

Yes, make sure that you understand the MVVM. It may be worth it to pick up the framework or to collect the basic library, if there have been developments.
Thanks for the reply. The program is a set of routines, small utilities which are used in our Department, divided by functionality into 4 groups. And a program tape is divided into 4 groups, each of which is a button that opens the required UserControl.
Decided while to leave everything in the same project. Was just thinking that the app will work better if progress would be to connect only the necessary UserControl's from libraries...
About MVVM - using DevExpress MVVM, like still missing head.
For the owner a special thank you, learning. - brycen commented on July 4th 19 at 23:40
July 4th 19 at 23:39
it is not necessary to rewrite each UserControl in a separate project (.dll) and then drag it into the main window?

First, each individual is no need to organize by task, second, the namespace can be in one DLL to make a different.

Visual Studio Team Services such as appropriate, from where to start learning this service?

As well as everything else you study.
July 4th 19 at 23:41
On BitBucket look gives you to create private repositories, unlike GitHub.

Find more questions by tags .NETVisual Studio