503 reputation
415
bio website
location Minneapolis, MN
age 29
visits member for 3 years, 7 months
seen Apr 1 at 15:03

I like to program, but am a noob, which is why I'm here.
<-My sexy fatbooth picture


Dec
18
awarded  Notable Question
Sep
24
awarded  Autobiographer
Dec
10
awarded  Notable Question
Nov
25
awarded  Popular Question
Oct
2
awarded  Popular Question
Jul
19
awarded  Popular Question
May
31
awarded  Yearling
May
23
awarded  Popular Question
Nov
25
awarded  Popular Question
Oct
15
awarded  Popular Question
Aug
13
awarded  Popular Question
Jun
26
comment How should I structure a solution for a long term project?
C# .net ............
Jun
26
comment How should I structure a solution for a long term project?
I totally forgot to even consider how namespaces play into this. I'm mainly looking for a best practice and not looking stupid by doing what is intuitive to me (which can often times be stupid).
Jun
26
asked How should I structure a solution for a long term project?
May
31
awarded  Yearling
Feb
3
comment Organizing projects in SVN
Let me know what you think of this. Even with locks, I'm still a little resistant to use them and incorporate all of our project files into an SVN trunk. The reason for this is if I want to make a modification to an Excel report, I have to update to the most recent version, make my changes, save them, and then check them in. For more technical source code files, I think this procedure is ok, but for excel files that have to be used by a lot of people, I think there would be a lot of pushback if everyone had to have SVN just to view them.
Feb
3
comment Organizing projects in SVN
I'm wondering if you should put trunk, branches, and tags in SVN\Projects or in SVN\Projects\Project1, SVN\Projects\Project2 etc
Feb
3
comment Organizing projects in SVN
I just tried making modifications to a .xlsx file and checking it in and making modifications of the same file in a different checkout. The conflicts were really impossible to read, it seems best too keep these out of SVN since because conflicts are so poorly handled, collaboration isn't as easy.
Feb
3
comment Organizing projects in SVN
@unholysampler, is it standard to have trunk, branches, and tags directories per project? That's something else I was wondering about. Currently in SVN we have things split up by language, and each language folder has the trunk, branches, and tags folders inside. It sounds like from the comments here that we'll split things up by project, but I'm still unclear if there should be these trunk, branches, and tags folders for the entire projects folder, or per project folder. Thanks :)
Feb
3
comment Organizing projects in SVN
@AndresF., I completely agree with you, this is an idea my coworker is suggesting. His reasoning is that with checked out SVN files on the shared drive, there's not another location for people to find files associated to a project. That's just another level of complexity that will make life a lot more difficult for the non-technical people on our team. It does certainly defeat the purpose of SVN in my ways, but it makes things a little easier. I came here to see if anyone else agreed with his idea or if there is a better alternative.