Guest Posted December 4, 2007 Report Share Posted December 4, 2007 Just one more thing. This problem is fixed on Visual Studio 2005, though it is always convenient to place your projects on a further path than your solution file. Kind Regards Link to comment Share on other sites More sharing options...
danipen Posted December 5, 2007 Report Share Posted December 5, 2007 Hi Jim, By your explanation I see that you have found a bug on Visual Studio 2003. The behavior you are talking about is due to the disk structure you have chosen for your solution and project files (.sln and .csproj). You can avoid this problem by tidying these files on disk. Could you please let us know how you have organized the mentioned projects and solution? We would just need to know where the .sln and .csproj are located. Regards Link to comment Share on other sites More sharing options...
Guest Posted December 5, 2007 Author Report Share Posted December 5, 2007 Sure! I have two "ClassLibrary" depending on a solution. The structure is as follows: /MyProject | | |_ ClassLibrary1 | | | |_ ClassLibrary1.csproj | | |_ ClassLibrary2 | |_ .sln | |_ ClassLibrary2 | |_ ClassLibrary2.csproj Regards Link to comment Share on other sites More sharing options...
danipen Posted December 5, 2007 Report Share Posted December 5, 2007 Hi again Jim You should reorganize your projects in order to have the following disc structure: /MyProject | | |__ ClassLibrary1 | | | |_ ClassLibrary1.csproj | |__ ClassLibrary2 | | | |_ ClassLibrary2.csproj | |__ .sln Or, as a alternative, you also can use this other configuration: /MyProject | | |__ ClassLibrary1 | | | |_ ClassLibrary1.csproj | | |__ ClassLibrary2 | | | |_ ClassLibrary2.csproj | |__ SolutionDir | |_ .sln Please, let us know if this solves your problem. Link to comment Share on other sites More sharing options...
Guest Posted December 5, 2007 Author Report Share Posted December 5, 2007 Great!, It worked. Thanks a lot for your help Regards Link to comment Share on other sites More sharing options...
danipen Posted December 5, 2007 Report Share Posted December 5, 2007 Just one more thing. This problem is fixed on Visual Studio 2005, though it is always convenient to place your projects on a further path than your solution file. Kind Regards Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.