dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

cvs scc plugin generating several subdirectories

( CVSSCC )
Type: Public Status:Closed Created: 18 Feb 04 02:00 Updated: 11 Mar 04 03:00
--> Igor Pushkov (admin)  at 11 Mar 04 03:00 writes

) - proposing a module name not equal as the solution name in case of a
\'unified root\'
Afraid not, plug-in just display what pass IDE (VS .NET) to it. You
need think which module you want to put LOCAL PATH folder. The similar
issue exist for web projects. VS .NET suggest by default module name
which is not part of Solution module. This will work, but good
practice to place all project under the same module in CVS. But for me
this is not a big problem since this operation (add to CVS) occurs not
so often.
) - doing a delete of this file : \'*.vsscc,v\' in the repository
We tried to play around this. Block adding of that file is impossible,
since IDE fail 'Add to source control operation' if file not added. It
is possible to block it listing (i.e. even if it is in CVS we will not
inform IDE about this). However, I not sure what this file really
mean, and what is it purpose. Until this will not clear, I afraid to
make that fix.
Anyway, hope that no your issue solved.
--> Eric (user)  at 11 Mar 04 03:00 writes

This trick did it, it works fine, on the condition that :
1. when I put the solution under source control, the plugin is proposing as
module name the same name as my solution, but that can't be used : you MUST
use another name!!!!! (otherwise visual studio will not find your solution
anymore!!!)
example : the name of my solution was : HRSQLUpdater. For the name for the
module name, I did take : HRSQLUpdater_Root

2. after this I found in CVS the following directories in the repository :
\HRSQLUpdater_Root with two subdirectories
\HRSQLUpdater
\Tools

3. in the subdirectory : HRSQLUpdater, I deleted the file
'HRSQLUpdater.vsscc,v'

4. Then I deleted everything of this solution on my local disk and I did a
'Open from source control' :
as module name I give : HRSQLUpdater_Root\HRSQLUpdater.
Visual Studio asked me the solution file and putted everything on my disk
again in the right directories!!

So, my question is : can the plugin do this automatically?
I mean :
- proposing a module name not equal as the solution name in case of a
'unified root'
- doing a delete of this file : '*.vsscc,v' in the repository
--> Igor Pushkov (admin)  at 10 Mar 04 03:00 writes

Finally I found problem. It is so stupid, and I so angry to MS... I spend
so many time to find it... :(
When you add solution, for which "unified root" is not equal to the
solution folder VS .NET add some stupid file with extension .vsscc near the
solution. I not see anywhere in docs what this file can mean, but think
this is some "black hole fix" for SourceSafe. When this file exist in CVS,
VS .NET pull this file first, look at it, and create unneeded subfolder.
Then pull the .sln file not to the path you point, but into this
subfolder.
Solution for problem is simple, after you add your project, go to the
repository folder and delete that file. After that solution is pulled
without problems.
Think you should add this to the FAQ and HELP. Let me know if this will not
help.
--> Eric (user)  at 04 Mar 04 03:00 writes

Ha, sorry to bother you then. I misinterpreted the message :-(
Thanks
--> Igor Pushkov (admin)  at 04 Mar 04 03:00 writes

'accepted' means that we currently work on this problem. Hope it will
be really solved soon. I will notify you.
--> Eric (user)  at 04 Mar 04 03:00 writes

Hello Igor,

I shaw that the status of this ticket changed to 'accepted', but I have no
direct solution to my problem.

Because I couldn't wait anymore, I commited the project into CVS. I deleted
the 'giving problems projects' from the solution before I commited the
solution. Afterwards I added again these projects with an 'exclude from
source control' for the files not under the same directory.

I reread the articles of Microsoft concerning the 'unified root', this is
really the solution of the problem, but it appears that the plugin isn't
supporting this yet... :-(

Nevertheless we shall use the plugin, and we will order more licences.
I hope that a 'unified root' solution will be soon implemented in the
plugin.

Regards
--> Eric (user)  at 25 Feb 04 02:00 writes

as information : I use CVS Linux
--> Igor Pushkov (admin)  at 25 Feb 04 02:00 writes

Hm... CVS NT really not support this - ".". Let me think some more...
--> Eric (user)  at 25 Feb 04 02:00 writes

See following error screen
error.bmp 
--> Eric (user)  at 25 Feb 04 02:00 writes

yes, only the dot, nothing else
--> Igor Pushkov (admin)  at 25 Feb 04 02:00 writes

You put single dot, without quotes? Please see the attached picture.
singledot.gif 
--> Eric (user)  at 25 Feb 04 02:00 writes

When I put as module name "." (a single dot), he's giving me an error : not
a valid module name
Regards
Eric
--> Igor Pushkov (admin)  at 25 Feb 04 02:00 writes

If you have local path "p:\" this means that your project include
something that are not under "p:\hraccentSolutions\".
I simulate your project structure and can achieve this only this way.
If all files are under "p:\hraccentSolutions\" local path _should_ be
not "p:\" but "p:\hraccentSolutions\".
!!!! To not spend time more searching way VS .NET supply "P:\" as local
path try the other simple solution, that I suggest you previously.
Adding your solution select "." (single dot as module name). In that
case you should have CVS repository with the same structure as you
local file system.
--> Eric (user)  at 25 Feb 04 02:00 writes

problem with this workaround :
Our development tree :
p:\hraccentSolutions\HRSQLUpdater
p:\hraccentSolutions\Tools\NScript
I want to put HRSQLUpdater under source control :
If I understood you well :
the module name : 'hraccentSolutions' ?
local path : 'p:\hraccentSolutions' ?
There is one problem : the module name I can set, but the local path I
can't, it is grey and not selectable and editable....
Default the local path in the Bind to CVS dialog is : p:\
After the put under source control I find on my cvsroot :
hraccentSolutions/hraccentSolutions/HRSQLUpdater
Maybe one particular item I didn't mention yet : we are working with the
dos
command : 'subst' to create a virtual drive P: to have on every machine the
same structure.
On my machine for example I have the real structure :
c:\visual studio projects\hraccenSolutions\HRSQLUpdater
with the dos command : subst p: "c:\visual studio projects"
this wil give a drive P
p:\hraccentSolutions\HRSQLUpdater
But I tested it also directly on my C-drive with the source control, same
result...
see also the screens copies
pushok.doc 
--> Igor Pushkov (admin)  at 25 Feb 04 02:00 writes

Yes, you correct, with your folder organization all your solutions will
have same "unified root" and as result same module 'visual studio
projects'.
--> Eric (user)  at 25 Feb 04 02:00 writes

So to put everything on one line:
Our development tree :
c:\visual studio projects\HRSQLUpdater
c:\visual studio projects\Tools\NScript
c:\visual studio projects\HRTimeManager
c:\visual studio projects\HRPlanningManager
c:\visual studio projects\HRTools
Every solutions refers to Tools\NScript
I want to put HRSQLUpdater under source control :
If I understood you well :
the module name : 'visual studio projects' ?
local path : 'p:\visual studio projects' ?
And for the other solutions : the same thing?
-----Original Message-----
From: Pushok Software [mailto:support@pushok.com]
Sent: woensdag 25 februari 2004 13:29
To: Eric
Subject: Re: [pst8] cvs scc plugin generating several subdirectories
http://www.pushok.com/tickets_messages.php?id=8
When you add folder to source control it ask you for module name. You
type "hrsqlupdater" while should "visual studio projects". Module name
should correspond to local folder name.
I am try to explain. You press "add to source control" command, VS NET
found the "unified root" as "c:\\visual studio projects\". Then it
show bind to CVS and "ask" you to which module belongs this folder
(c:\\visual studio projects\).
Please try to add it again, specifying other module name. And send me
screen shoot of first "Bind to CVS" dialog.
--> Igor Pushkov (admin)  at 25 Feb 04 02:00 writes

When you add folder to source control it ask you for module name. You
type "hrsqlupdater" while should "visual studio projects". Module name
should correspond to local folder name.
I am try to explain. You press "add to source control" command, VS NET
found the "unified root" as "c:\\visual studio projects\". Then it
show bind to CVS and "ask" you to which module belongs this folder
(c:\\visual studio projects\).
Please try to add it again, specifying other module name. And send me
screen shoot of first "Bind to CVS" dialog.
--> Eric (user)  at 25 Feb 04 02:00 writes

Hello,

1. I did place the solution to a second level
c:\visual studio projects\hrsqlupdater
c:\visual studio projects\tools\nscript (directory of files referenced in
the solution hrsqlupdater)

After I did a 'add to source control' of the hrsqlupdater solution, I found
on the CVSROOT
/hrsqlupdater/visual studio projects/hrsqlupdater

--> I have now a second directory : this is not realy a solution...

When I do a 'open from source control' : he is again asking for each sub
project the module name...

2. I tried to use the dot "." (only the dot)
--> error message : not a valid module name


Maybe this is a specific .NET 2003 visual studio problem?
--> Igor Pushkov (admin)  at 20 Feb 04 02:00 writes

Erik, I checked option you mentioned in links. It has no effect for plugin,
since this
behavior already can be controlled by hands.
But, this articles help me to find simple solution for your problem.
Our plug-in, when shou you bind to cvs dialog allows controll manually _do
you want to create
solution module or not_. You can create it, or select existing. in terms of
this article selecting of
existing module equal to switching on mentioned option, creating module
equal to switching off
this option.
For your particular case you jsut need to type "." (single dot) as module
name, which will mean
that you add to to the root folder of CVS repository. This will solve your
problem, without
changing nothing. However, placing of all files to some second level folder
still considered as
the best options for you.
--> Igor Pushkov (admin)  at 20 Feb 04 02:00 writes

Eric, do you have success with this. Any more help needed?
--> Igor Pushkov (admin)  at 19 Feb 04 02:00 writes

Unfortunately I not have VS 2003 installed in my PC, as I need VS 2001
for development (7.0). It is not seems that this version have this
option (I checked the registry). I will check this in nearest one or two
days.
However, I think, this should work, if you enable this.
If not, you always can use option (1 -Move projects from root to second
level folder). In terms of mentioned article this will change your
"unified root" from "P:\" to something like "P:\Work" or
"P:\Solutions"
Anyway, even if it will be possible to add to project files which are
on other drives, adding of system files not good idea. And if you want
to add only your own files, place them under "unified root" which is
not root drive (C:\Solution or C:\Work, but not the C:\)
--> Eric (user)  at 19 Feb 04 02:00 writes

Visual .NET 2003 is doing this automatically.
At the end of the article, they are writing the following :
"Note At the time this article was written, not all source code control
providers implemented support for creating solution roots. Please contact
your source code control provider vendor for further information. The
Visual
SourceSafe 6.0d provider does support solution roots."
Does the plugin support this?
Regards
--> Igor Pushkov (admin)  at 19 Feb 04 02:00 writes

Hm... as usual, some MS trick... did you try it? Is it help?
--> Eric (user)  at 19 Feb 04 02:00 writes

Hello,

I found another link concerning the root folder under source control :

http://blogs.msdn.com/korbyp/archive/2003/08/05/54094.aspx
--> Eric (user)  at 19 Feb 04 02:00 writes

The problem with this solution 2 is that these compiled files will not be
under source control.
Normally we don't want to have exe, dll under source control, but in this
case, I want them under source control, because when I retrieve a version
tag of my project, I must be sure that these external exe/dll will work
with
my program!
(for exemple : when I build today version 1.0 of my project, I use version
2.3 of these external exe/dll. Suppose that a year later, I have version
2.2
of my project and that the external exe/dll is at version 4.0. For some
version 2.3 of these external exe/dll and not the version 4.0 !!)
I searched the net and found this link :
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechar
t/html/vsconSlnRootinVSS.asp
Did you implemented this in the plugin?
CVS is doing somekind of a root, but when 'opening a solution from source
control', he is asking always the 'open from' question.
This is normally corrected in .NET 2003...
Regards,
Eric
-----Original Message-----
From: Pushok Software [mailto:support@pushok.com]
Sent: woensdag 18 februari 2004 15:42
To: Eric
Subject: Re: [pst8] cvs scc plugin generating several subdirectories
http://www.pushok.com/tickets_messages.php?id=8
I checked your debug logs, and found that problem:
Your solution contain files that are not under the P:\HRSQLUpdater:
File P:\Tools\Nscript\bin\Release\NScriptLib.dll, status 257
File P:\Tools\Nscript\bin\Release\NScriptw.exe, status 257
File P:\Tools\Nscript\bin\Release\NScript.exe, status 257
Not know to witch project they included, however because of this
VS.NET consider as you root local path "P:\" instead of
P:\HRSQLUpdater
The solution can be:
1. Move projects from root to send level folder
* Move both folders: "HRSQLUpdater", "Tools" to some second level
folder like: Solutions
* Add solution from this location, local path will be "P:\Solutions",
module should be "Solutions"
* Opening project from source control point as local path:
2. Intelligentadding
* Before adding of project to source control exclude
File P:\Tools\Nscript\bin\Release\NScriptLib.dll, status 257
File P:\Tools\Nscript\bin\Release\NScriptw.exe, status 257
File P:\Tools\Nscript\bin\Release\NScript.exe, status 257
* Normally, if no any such file in project local path will be
P:\HRSQLUpdater, choose as module "HRSQLUpdater"
* Then add to project
File P:\Tools\Nscript\bin\Release\NScriptLib.dll, status 257
File P:\Tools\Nscript\bin\Release\NScriptw.exe, status 257
File P:\Tools\Nscript\bin\Release\NScript.exe, status 257
* They appears in pending checkins. At this moment, select them in
solution explorer and apply command "File\Source Control\Exclude files
from source control"
* After that you will see red "block" icons on these files, and they
disappear from pending checkins. This way you inform VS .NET that
files are in solution, but not needed to place them to Source Control.
Unfortunately it is impossible to do "before" you add project to
source control.
However, in normal life, project added to source control parts by
parts, and it is not hard to exclude some auto-generated files from
source control
I suggest option 2
--> Igor Pushkov (admin)  at 18 Feb 04 02:00 writes

I checked your debug logs, and found that problem:
Your solution contain files that are not under the P:\HRSQLUpdater:
File P:\Tools\Nscript\bin\Release\NScriptLib.dll, status 257
File P:\Tools\Nscript\bin\Release\NScriptw.exe, status 257
File P:\Tools\Nscript\bin\Release\NScript.exe, status 257
Not know to witch project they included, however because of this
VS.NET consider as you root local path "P:\" instead of
P:\HRSQLUpdater
The solution can be:
1. Move projects from root to send level folder
* Move both folders: "HRSQLUpdater", "Tools" to some second level
folder like: Solutions
* Add solution from this location, local path will be "P:\Solutions",
module should be "Solutions"
* Opening project from source control point as local path:
2. Intelligentadding
* Before adding of project to source control exclude
File P:\Tools\Nscript\bin\Release\NScriptLib.dll, status 257
File P:\Tools\Nscript\bin\Release\NScriptw.exe, status 257
File P:\Tools\Nscript\bin\Release\NScript.exe, status 257
* Normally, if no any such file in project local path will be
P:\HRSQLUpdater, choose as module "HRSQLUpdater"
* Then add to project
File P:\Tools\Nscript\bin\Release\NScriptLib.dll, status 257
File P:\Tools\Nscript\bin\Release\NScriptw.exe, status 257
File P:\Tools\Nscript\bin\Release\NScript.exe, status 257
* They appears in pending checkins. At this moment, select them in
solution explorer and apply command "File\Source Control\Exclude files
from source control"
* After that you will see red "block" icons on these files, and they
disappear from pending checkins. This way you inform VS .NET that
files are in solution, but not needed to place them to Source Control.
Unfortunately it is impossible to do "before" you add project to
source control.
However, in normal life, project added to source control parts by
parts, and it is not hard to exclude some auto-generated files from
source control
I suggest option 2
--> Eric (user)  at 18 Feb 04 02:00 writes

Hello,

This message is for Igor Pushkov.
I was emailing with him for a specific problem.
He sended me a debug dll and asked me to send him the debug log file.

Did the debug file helped to find the problem?
Can I do something else to help?

Regards,
Eric Van Bocxlaer
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful
You are 9541971 visitor since 20 Jan 2003.
1104 visitors today and 3 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com