Home/ Questions/Q 705137
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T04:01:11+00:00

I have a WPF application (KaleidoscopeApplication) organized as follows: Solution (6 projects) Cryptography (DLL)

  • 0

I have a WPF application (KaleidoscopeApplication) organized as follows:

  • Solution (6 projects)
    • Cryptography (DLL)
    • Rfid (DLL)
    • KaleidoscopeApplication (buildable “startup project”)

Basically, KaleidoscopeApplication contains a bunch of resources (sounds, images, etc) and your standard WPF junk (App.xaml, App.xaml.cs, other xaml and code).

I need to create a new application that is very similar to Kaleidoscope, but I’m not sure of the best way to organize. This new app will need access to much of the same code and resources as Kaleidoscope. Preferably, I would like to create a new project in the solution, then simply use the “set as startup project” to pick which app I want to build. However, will I be able to access (share) the Resources folder of Kaleidoscope?

I know I will be able to access much of the code if I simply add a reference to the project and include a “using Kaleidoscope”. But the resources I’m not so sure about.

Is this the right way to organize or am I asking for trouble in the future?

Thanks in advance!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The recommended solution in this case would be to refactor the resources and any common required code into a separate Assembly that both UI applications could use. You will probably need to do some manual tweaking to make sure everything is exposed the way you need it to be, but it’ll make things cleaner in the long run.

    • 0