Don't comment the topic if you have a new question.
You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.
By symbolic, 5 January, 2011
Dear Guys @ Gurux and all forum members,
Happy New Year! and I hope you all be well.
I just updated my local repo with the rev. 141 and I saw the shared folder is duplicated on each project. Although it may resolve the previous problem of linking the projects in Visual Studio, now it raises a new bigger one and that's code redundancy.
I'm wondering how are you guys going to have the files synchronized with each other whenever one of the shared .h or .cpp files are going to change.
I think the best resolution to this problem is to change all the #include directives to point to "Shared\C++" or "Shared\ManagedC++" and the same for the .idl references and then change the according project properties to search for the appropriate folders as include directories. I did that before and it worked perfect.
I understand your point of view. In early days we worked exactly like this. We changed the behavior because our users had a lot of problems with it. This works excellently if all developers have the same directory structures.
We have a lot of developers who are taking only one project and work with it. Usually they are copying this project to just one directory. This is the reason we want all nesessary files are under the selected project.
Earlier we worked with Source Safe and there was no problems to share files between different projects. Because SVN can't
share files, only directories, we moved all shared files to one directory. I'll have to say that this is BIG limitation in SVN.
In our internal SVN we are using shared directory as you suggest, but when we release new version and update code to SourgeForge, we will copy files to those directories.
So there is no worry about code redundancy.
I really appreciate your idea.
We just updated our version publishing system and there was a problem that it did't copy all Shared directories. This is fixed now and everything should work from now on.
Re: Source Redundancy
Hello,
I understand your point of view. In early days we worked exactly like this. We changed the behavior because our users had a lot of problems with it. This works excellently if all developers have the same directory structures.
We have a lot of developers who are taking only one project and work with it. Usually they are copying this project to just one directory. This is the reason we want all nesessary files are under the selected project.
Earlier we worked with Source Safe and there was no problems to share files between different projects. Because SVN can't
share files, only directories, we moved all shared files to one directory. I'll have to say that this is BIG limitation in SVN.
In our internal SVN we are using shared directory as you suggest, but when we release new version and update code to SourgeForge, we will copy files to those directories.
So there is no worry about code redundancy.
I really appreciate your idea.
We just updated our version publishing system and there was a problem that it did't copy all Shared directories. This is fixed now and everything should work from now on.