Skip to main content
deleted 184 characters in body
Source Link

Context: I'm creating some applications to help me on my daily tasks, it does not connect anywhere and the only "data" it has to deal with is the parameters that I enter on the input fields.

This is how I structured my solution:

|- Helpers (Folder + Class Library)
|- Core (Folder + Class Library)
|- Shared (Folder + Shared project)
|- Apps (Folder + WPF Projects)
|---- App1 (WPF Project)
|---- App2 (WPF Project)
|---- App3 (WPF Project)

While developing the first application (App1) I've created a few UserControls. Now I want to use those user controls on the second application (App2).

Question is: Should I create a new project to hold all these UserControls and reference it from App1, App2 and App3? Should it be a WPF Project?

If not, what should I do?

Additional info: I'm using MVVM.

Ps: Please know that I'm a student, so it'd be nice if the answers contain a start point, or some of the advantages and disadvantages of each approach, so I can learn them better.

Thank you!

Context: I'm creating some applications to help me on my daily tasks, it does not connect anywhere and the only "data" it has to deal with is the parameters that I enter on the input fields.

This is how I structured my solution:

|- Helpers (Folder + Class Library)
|- Core (Folder + Class Library)
|- Shared (Folder + Shared project)
|- Apps (Folder + WPF Projects)
|---- App1 (WPF Project)
|---- App2 (WPF Project)
|---- App3 (WPF Project)

While developing the first application (App1) I've created a few UserControls. Now I want to use those user controls on the second application (App2).

Question is: Should I create a new project to hold all these UserControls and reference it from App1, App2 and App3? Should it be a WPF Project?

If not, what should I do?

Additional info: I'm using MVVM.

Ps: Please know that I'm a student, so it'd be nice if the answers contain a start point, or some of the advantages and disadvantages of each approach, so I can learn them better.

Thank you!

Context: I'm creating some applications to help me on my daily tasks, it does not connect anywhere and the only "data" it has to deal with is the parameters that I enter on the input fields.

This is how I structured my solution:

|- Helpers (Folder + Class Library)
|- Core (Folder + Class Library)
|- Shared (Folder + Shared project)
|- Apps (Folder + WPF Projects)
|---- App1 (WPF Project)
|---- App2 (WPF Project)
|---- App3 (WPF Project)

While developing the first application (App1) I've created a few UserControls. Now I want to use those user controls on the second application (App2).

Question is: Should I create a new project to hold all these UserControls and reference it from App1, App2 and App3? Should it be a WPF Project?

If not, what should I do?

Additional info: I'm using MVVM.

Thank you!

Tweeted twitter.com/StackSoftEng/status/804179426682478592
edited title
Link

Should I create a (new) project for shared UserControls?

deleted 2 characters in body
Source Link

Context: I'm creating some applications to help me on my daily tasks, it does not connect anywhere and the only "data" it has to deal with is the parameters that I enter on the input fields.

This is how I structured my solution:

|- Helpers (Folder + Class Library)
|- DomainCore (Folder + Class Library)
|- Shared (Folder + Shared project)
|- Apps (Folder + WPF Projects)
|---- App1 (WPF Project)
|---- App2 (WPF Project)
|---- App3 (WPF Project)

While developing the first application (App1) I've created a few UserControls. Now I want to use those user controls on the second application (App2).

Question is: Should I create a new WPF Projectproject to hold all these UserControls and reference it from App1, App2 and App3? Should it be a WPF Project?

If not, what should I do?

Additional info: I'm using MVVM.

Ps: Please know that I'm a student, so it'd be nice if the answers contain a start point, or some of the advantages and disadvantages of each approach, so I can learn them better.

Thank you!

Context: I'm creating some applications to help me on my daily tasks, it does not connect anywhere and the only "data" it has to deal with is the parameters that I enter on the input fields.

This is how I structured my solution:

|- Helpers (Folder + Class Library)
|- Domain (Folder + Class Library)
|- Shared (Folder + Shared project)
|- Apps (Folder + WPF Projects)
|---- App1 (WPF Project)
|---- App2 (WPF Project)
|---- App3 (WPF Project)

While developing the first application (App1) I've created a few UserControls. Now I want to use those user controls on the second application (App2).

Question is: Should I create a new WPF Project to hold all these UserControls and reference it from App1, App2 and App3? If not, what should I do?

Additional info: I'm using MVVM.

Ps: Please know that I'm a student, so it'd be nice if the answers contain a start point, or some of the advantages and disadvantages of each approach, so I can learn them better.

Thank you!

Context: I'm creating some applications to help me on my daily tasks, it does not connect anywhere and the only "data" it has to deal with is the parameters that I enter on the input fields.

This is how I structured my solution:

|- Helpers (Folder + Class Library)
|- Core (Folder + Class Library)
|- Shared (Folder + Shared project)
|- Apps (Folder + WPF Projects)
|---- App1 (WPF Project)
|---- App2 (WPF Project)
|---- App3 (WPF Project)

While developing the first application (App1) I've created a few UserControls. Now I want to use those user controls on the second application (App2).

Question is: Should I create a new project to hold all these UserControls and reference it from App1, App2 and App3? Should it be a WPF Project?

If not, what should I do?

Additional info: I'm using MVVM.

Ps: Please know that I'm a student, so it'd be nice if the answers contain a start point, or some of the advantages and disadvantages of each approach, so I can learn them better.

Thank you!

Source Link
Loading