From: Wendy Elizabeth on 27 Jun 2010 14:57
"Mr. Arnold" wrote:
I want to mention the following:
1. To compile the big solution for the first time, I need to compile the
code outside of the 'subversion' version control software? Basically, I would
need to get out all
references to the 'subversion' source control for the first time?
2. All the code is in subversion source control, so I need to get all the
from that location.
3. Should I look at 'subversion' source control 'help' on the internet to
see why I lose references to projects within in the same solution? Basically
should I look at the 'subversion' version control online help to see the time
of items that can be lost when a .net solution is checked in and how to solve
You are probably right that I may need a contractor for a short period of
time to help me.
"Mr. Arnold" wrote:
> Wendy Elizabeth wrote:
> > "Mr. Arnold" wrote:
> > You answered most of my extra questions but I still have a few more
> > additional questions based upon your last response which are:
> > 1. This pertains to obtaining the 'latest version' subversion:
> > a. What do you do to obtain the 'latest' version in subversion? Are
> > there some commands you execute?
> It has to do with going to the code repository, I am sure you have
> something, and getting the latest version of all the code out of the
> repository. It has to do with you knowing how to work with the code
> repository solution to accomplish it.
> > b. The subversion that the programmer used that checked this code in left
> > some time ago and this company had a different location for subversion. There
> > was some kind of a problem with the original location for subversion, so a
> > 'new' network person at this company changed the location of the subversion I
> > checked out code from. Could using a different location for subversion cause
> > a problem? Should I go try to check out the code from the original location
> > where the code was checked into subversion?
> It comes back to this. If this is the first time you have tried to
> compile this solution, then you need to get the latest code/projects
> (all of the projects -- all of the code) out of the repository and
> compile the entire solution (all of it all of the projects) the first
> time, before you can compile a subversion.
> You have to compile the entire solution the first time, because if you
> compile the subversion the first time, things will not be there that the
> subversion of projects are looking for (references to other projects)
> outside of the subversion of projects that will lead to compile errors
> for the subversion.
> If you have not done this, then you have to do it. You can't go to the
> subversion initially and compile it, because those projects may be
> looking for references to other projects that are outside the subversion
> and they are not there (DLL's) compiled from other projects referenced
> are not there physically on your development machine.
> > 2. Project Reference for each project
> > To add a project reference for each project, can could expand upon:
> > If you're in the IDE and you're at a project, then expand the
> >> "Reference" section. If you see the "yield sign symbol" next to a
> >> reference line, then you know you may have problems with reference to a
> >> DLL the project is using.
> > Basically I would then select 'add a reference' by right clicking on the
> > situation listed above.. From the tabbed items I could select, I know there
> > are about four tabs like '.net', com, and two more tabbed items. Which tab
> > would I select? Once I pick the correct tab, would kind of an item would I
> > need to select to add the correct reference?
> What path to take is based on what type of reference is needed. If its a
> .NET Framework reference, the (.NET), if it's a 3rd party DLL, then
> you need to 'Browse' to the location of the DLL you have on the machine,
> and if it's by project reference, then you have to 'Browse' to the
> location of the project file on the machine and use it.
> > 3. Is there a way to tell when a project should be referenced by the
> > referenced > project's DLL) and when the project should be referenced by
> > using (Project Reference by project)? If so, how can you tell this?
> None of the projects should be using a DLL for project reference. All
> projects should be using (Project Reference). Because when you use
> 'Project Reference' the complier knows to go find the DLL for other
> projects by itself without you needing to point to it yourself.
> > 4. The following pertains to a dll:
> > a. Where would I look to obtain a few dll's that are missing in the
> > solution?
> You have to determine what the DLL(s) are .Net Framework, 3rd party or
> DLL created from compiling a project.
> I would say your biggest problem may be is that you have not compiled
> the entire solution first to get project DLL(s) on the machine before
> you tried to compile a subversion of projects, because those projects
> are looking for reference to projects outside the subversion that have
> not been complied.
> > b. If I can not find some dll's, is there a way to tell what code in the
> > solution I should to use to compile (build) the dll (executable)?
> Why bother? If this solution is one big solution of projects, then
> compile the entire thing not the subversion or an individual project,
> and it will work itself out.
> > C. Can you tell me how to compile the separate dll's and how to add the
> > separate dll's into the solution?
> Take note on everything I have told you prior to this point.
> > Your help has been one of the best I have ever seen for people! Thank you
> > again very much!
> > So you are saying each project has its own a projectname.csproj file? (I
> > was assuming that the entire solution had only one csproj file.)
> A solution has a main .sln file that holds all of the project for the
> entire solution, and you can tell it to compiler to use the .sln file
> and do the compile of all projects in the .sln.
> You can have a .sln file that has a subversion of projects and any
> common projects (core projects) that the subversion of projects have
> reference to outside of the subversion of projects.
> Maybe, you need a contractor in there for a short time to help you
> figure this out and what you need to do.
> HTH and good luck to you.....
From: Mr. Arnold on 27 Jun 2010 15:20
Wendy Elizabeth wrote:
> "Mr. Arnold" wrote:
> I want to mention the following:
> 1. To compile the big solution for the first time, I need to compile the
> code outside of the 'subversion' version control software? Basically, I would
> need to get out all
> references to the 'subversion' source control for the first time?
Including the subversions and compile it all at onetime.
> You are probably right that I may need a contractor for a short period of
> time to help me.
I would suggest that you go back to your boss and tell he or she that
you need some hands on guidance from an experienced contractor that has
worked with a large multiple projects solution.