How to share the common project across different solution to maintain the same instance

Question

0.00/5 (No votes)

See more:

I have a class "Student", this class is used in ProjectA in solution1 and same class used in ProjectA in Solution2

I have changed something in Student classfrom solution1, that changes not reflected in solution2, still its holding the previous.

My problem is : How to share the project between 2 UI, when something changes from solution1 and that should be reflected in solution2, so how to maintain the single instance of Student class across different UI.

What I have tried:

I'm using dependency mechanism in prism but its working between the modules, but not between the solution and different UI

Posted 14-Nov-19 19:59pm

sheik SHA

Updated 14-Nov-19 20:28pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2019-11-14T20:29:00

Solution 1

There are two ways to include a project in a solution:
1) You can add a reference to the Assembly to the new project. THis just gives the new project access to the classes in the added project.
2) You can add an existing project to a solution. This allows you to edit the code of the added project from either solution.

Neither of these will automatically "update" Solution1 or Solution2 if the added project is changed in the other - it requires a rebuild of both projects to use the new version.
And if you think about it, that's exactly what you want to happen.
Why? Let's look at what would happen if asn edit automatically updated both. Suppose it doesn't work immediately; it has a catastrophic bug? Both applications fail, despite one of them not "knowing" about any changes! That's bad: you shouldn't "break" existing code!

So add your project to both solutions, and then build both solutions when the "common project" is stable. That way, the "unaffected app" doesn't fail because the common project changed in the meantime.

Posted 14-Nov-19 20:29pm

OriginalGriff

Comments

sheik SHA 15-Nov-19 6:24am

Thank you for you solution, currently we are using the same that you have mentioned.

Sorry i didnt explain my question clearly.

What i need: during compile time its fine, please consider the following scenario

Both applications are running
- initially student object contains Name property and the value is "XXXX"
- after running both application, solution 1 reading the Name property and the return value is "XXXX" also read from solution2 and return same "XXXX".
- Then solution1 change the name to "YYYY" and solution2 reading the name again, my expectation is the name should be "YYYY" but its return same "XXXX", which shows both application using same code during compile time but maintain 2 different instance on run time.

OriginalGriff 15-Nov-19 6:46am

Right ... that is not going to happen. The two applications have totally separate memory, and what happens to one object in AppA does not, cannot, and will not affect an object in AppB, even if they share classes.

What you need is "intermediate storage" which holds the information that is used by both AppA and AppB: I'd suggest that you look at a DB, probably server based since you effectively need multiple users accessing it at the same time.
The other solution is to have the two apps communicate between themselves, but that's complicated and "locks" the two apps together - it's possible, but if you later add AppC it starts to get exponentially more complicated. A DB is a better solution here, really!

sheik SHA 15-Nov-19 6:54am

Thanks for your reply and effort :)

OriginalGriff 15-Nov-19 6:55am

You're welcome!