>>If I create a UserControl in solution A, then reference it in solution B, then go back to solution A and make a change, how do I ensure that the change makes it to solution B?
>
>I assume you mean:
>>If I create a UserControl in
a project in solution A, then reference
that project in solution B, then go back to solution A and make a change, how do I ensure that the change makes it to solution B?
>
>If so then the answer is that it should be automatic when the solution is rebuilt. If it's not what you meant please expand...
>Best,
>Viv
No, there are two different solutions.
I have a usercontrol in it's own solution in it's own folder. One project in a stand alone solution.
Then want to use the control it in a separate WinForms project. So in my WinForm project I created a reference to the user conrol. .Net makes a copy of the control's DLL in the WinForm's project Bin folder.
I then go back to the user control solution and make a change. The copy of the DLL containing the user control that's in the WinForm's Bin folder is now out of date.
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people