Access is denied, multiple project solution

[Toe Dipper]

Basically looking for advice on structuring projects in solutions.

Here is our example.
We have a custom windows control. This control is then in used in 4
different projects. In VB6 we would have just added the control
project to each project group.

Solution 1
Windows app
Custom control

Solution 2
Windows app2
Custom control

In short, any time we create a custom solution that uses other
projects we get access denied errors.

1. How should we be structuring our libraries and controls?
2. How do we debug these considering their use is likely different in
each project that uses them.

Thanks
Glenn

[Toe Dipper]

On Mon, 10 Jul 2006 16:22:53 -0400, Toe Dipper
<to*******@discussions.microsoft.comwrote:

>Basically looking for advice on structuring projects in solutions.

Here is our example.
We have a custom windows control. This control is then in used in 4
different projects. In VB6 we would have just added the control
project to each project group.

Solution 1
Windows app
Custom control

Solution 2
Windows app2
Custom control

In short, any time we create a custom solution that uses other
projects we get access denied errors.

1. How should we be structuring our libraries and controls?
2. How do we debug these considering their use is likely different in
each project that uses them.

Thanks
Glenn

Since my first post I have realized that this is due to the project
directories being marked as readonly. So now my question would be why?

It would be common for us to create a solution that might hold three
projects in which case this solution would benefit from separate
folders for each project. Whereas by doing this we would prevent one
of the projects in the previous solution being used in a different
solution.