Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Source Safe / October 2004

Tip: Looking for answers? Try searching our database.

How to track 3rd party tools in Source Safe

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Robert Smith - 27 Oct 2004 16:59 GMT
Our application uses several 3rd Pary tools.  

One way to track the tools is to add the entire 3rd party installation CDs
into Source Safe.  That doesn't seem like a good practise.

We can put the Tool Installation CD's on a network but there is no way to
link the tool to the code in Source Safe that needs it to build.

Does anyone have a better practise?

Thanks for any suggestions....
Alberiton - 28 Oct 2004 09:41 GMT
Hello:
Why do you want to track the 3rd party tools?
Thanks
Alberition

> Our application uses several 3rd Pary tools.
>
[quoted text clipped - 7 lines]
>
> Thanks for any suggestions....
Robert Smith - 28 Oct 2004 13:59 GMT
So that 1 year from now, when someone needs to build the program to make a
bug fix, they can build it.

All the components neccessary to build a project should somehow be
associated with the source code.  There is more than one way to do this, I'm
looking for the best way.

> Hello:
>  Why do you want to track the 3rd party tools?
[quoted text clipped - 12 lines]
> >
> > Thanks for any suggestions....
Richard J - 28 Oct 2004 16:09 GMT
Robert,

But you won't be making bug fixes to these 3rd party tools.  Once they get
installed at your client site, they don't need to be installed again unless
there is a service pack or upgrade available.

And even then, it would seem like these 3rd party tools, as dependencies of
your project(s), would simply be included in the installation tool, whether
that is Installshield or Package and Deployment Wizard, etc.

> So that 1 year from now, when someone needs to build the program to make a
> bug fix, they can build it.
[quoted text clipped - 19 lines]
> > >
> > > Thanks for any suggestions....
Robert Smith - 28 Oct 2004 20:09 GMT
Let me try to explain the problem in a different way.

You are assigned the task of fixing a bug in a project you have never worked
on.
You get the code out of Source Safe and try to build it.
The build fails because you do not have a required Image Library installed
on your system.  

So where do you find the 3rd Pary Image Library?  

Maybe the original developer copied the Image Library Installation CD into
Source Safe.  Asside from the horrendous waste of space, this would work.

Maybe the original developer copied the Image Library Installation CD onto a
network drive.  Hopefully, he left a document somewhere in the Source Safe
project indicating this....and hopefully no one removed, or updated, the
library on the network drive.

Getting the Runtime 3rd Party components from your installation CD will not
help, you  need the SDK to compile and link, not the run-time components.

> Robert,
>
[quoted text clipped - 29 lines]
> > > >
> > > > Thanks for any suggestions....

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.