Thanks Carlos! I appreciate your time.
"Carlos J. Quintero [.NET MVP]" wrote:
> When you load VB.NET and C# projects in VS.NET, in the Solution Explorer
> under EACH project node there is a "References" node which lists the
> compiled assemblies (including 3rd party) that you need to compile that
> project. All the remaining is code in your solution. For example, if you see
> a "nunit.framework" in the References node, you know that you need NUnit.
> The same applies to 3rd party controls and libraries. I think that if a
> reference is not installed in the computer but the project references node
> list it, you get some kind of visual hint about the problem.
>
> --
>
> Carlos J. Quintero
>
> MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
> You can code, design and document much faster.
>
http://www.mztools.com >
>
> "Sean W." <SeanW@discussions.microsoft.com> escribió en el mensaje
> news:4F728E19-7E6A-4635-89D6-2F6E36D4AF1D@microsoft.com...
> > Thank You Carlos.
> >
> > I understand needing to install the third party items, especially if a
> > license is involved. My main concern is identifying those third party
> > items.
> > I have identified a couple such as Nunit and Configuration Application
> > Block. Is there a way to list all references used through-out the
> > solution?
> > My first assumption is to find one, install it on my box, recompile, keep
> > going until compile has zero errors. I'm hoping for a much easier way.
> > We
> > are not using Source Safe, yet. I'm working on getting it in for this
> > exact
> > reason.
> >
> > Thanks,
> >
> > Sean
>
>