J
Jeff
IDE: Visual Studio 2003 .net
OS: XP Pro
Question 1:
When I in Solution Explorer chooses "Add Reference" for to add reference to
a component (in the same solution, but on another project)... Shall I choose
the debug or release version of the component?
I ask because I get this warning when I build my solution:
Warning: The dependency 'GUI, Version=1.0.1654.13858, Culture=neutral' in
project
'winApp' cannot be copied to the run directory because it would
overwrite
the reference 'GUI, Version=1.0.1654.21871, Culture=neutral'.
*********************
Question 2
I created a form and placed a tab-controll on it. Then I created another
form by inheriting from this one. But I in the new form all the properties
on the tab-controll are disabled...
I thought this happend because the tab-controll was a private member of the
base-form, so I changed it to protected, but still the same effect... what
am I doing wrong here??
(The ancestor is in the GUI component, and the new form is in the winApp
project, maybe the reason is related to the warning message above)
I think this have something to do with the security level of the controll??
************************
Any clues will be appreciated!
Jeff
OS: XP Pro
Question 1:
When I in Solution Explorer chooses "Add Reference" for to add reference to
a component (in the same solution, but on another project)... Shall I choose
the debug or release version of the component?
I ask because I get this warning when I build my solution:
Warning: The dependency 'GUI, Version=1.0.1654.13858, Culture=neutral' in
project
'winApp' cannot be copied to the run directory because it would
overwrite
the reference 'GUI, Version=1.0.1654.21871, Culture=neutral'.
*********************
Question 2
I created a form and placed a tab-controll on it. Then I created another
form by inheriting from this one. But I in the new form all the properties
on the tab-controll are disabled...
I thought this happend because the tab-controll was a private member of the
base-form, so I changed it to protected, but still the same effect... what
am I doing wrong here??
(The ancestor is in the GUI component, and the new form is in the winApp
project, maybe the reason is related to the warning message above)
I think this have something to do with the security level of the controll??
************************
Any clues will be appreciated!
Jeff