10 messages in com.perforce.perforce-user[p4] Perforce and DLL hell| From | Sent On | Attachments |
|---|---|---|
| Steve Culshaw | 20 Mar 2004 04:24 | |
| Noel Yap | 20 Mar 2004 05:46 | |
| Steve Culshaw | 20 Mar 2004 06:06 | |
| Noel Yap | 20 Mar 2004 07:10 | |
| Rich Ireland | 20 Mar 2004 08:00 | |
| Bob Arnson | 20 Mar 2004 08:13 | |
| Noel Yap | 20 Mar 2004 08:17 | |
| ste...@vance.com | 20 Mar 2004 08:32 | |
| Keating, Tim | 22 Mar 2004 06:53 | |
| Steve Culshaw | 22 Mar 2004 09:00 |
| Subject: | [p4] Perforce and DLL hell |
|---|---|
| From: | Steve Culshaw (scul...@caps-solutions.co.uk) |
| Date: | 03/20/2004 06:06:33 AM |
| List: | com.perforce.perforce-user |
Noel,
thanks for the response - sorry I don't get it, and I'm new to this, so any comments are welcome, no matter how "obvious"
What I'm struggling on (well first thing) is how to cope with the issue of DLL registration in the Windows registry
Say I'm working on Release 2, and this has 20-30 DLL's, all registered, in my local hard disk, say C:\Release2\DLL\...
Then I have to switch over to work on a potential bug in Release 1, so I switch my client spec to the old one - Ok, I can sync to head and get the files, including DLL's (some older than in Release 2), say C:\Release1\DLL\...
But I believe that unless each DLL goes to exactly the same location on my hard disk, my registry means I'll use the new DLL's - if I say CreateObject("ComponentOne.PrintManager"), it'll be the ComponentOne DLL in C:\Release2\DLL\ComponentOne.dll
Confused, I know I am :-)
Cheers, Steve C.
-----Original Message----- From: Noel Yap [mailto:Noel.Yap at morganstanley.com] Sent: 20 March 2004 13:47 To: Steve Culshaw Cc: perforce-user at perforce.com Subject: Re: [p4] Perforce and DLL hell
I'm not sure I understand your question, but I'll take a stab at it. Please bear in mind that I'm not a Windows programmer and so may be assuming things that aren't true or missing things that would otherwise be obvious.
If you have release branches, the configuration (possibly within the makefile or a run script) of an older release branch should be pointing to the older version of the DLL. Therefore, have your client sync down the release branch and work from there.
HTH, Noel
Steve Culshaw wrote:
Can anyone point me at guidance on how to use Perforce with multiple versions of DLL's and Windows registration of DLL's
Say for e.g. - in my main line, I have a DLL say version 1.1, but in a released branch I have an older version 1.0. - we find a bug in the release in another component, so we want to work on it. - Ok, I can switch client spec's and sync to the release head, but I can still only have one version of the DLL registered, so I'm working against the DLL 1.1 in the main line
- I can't believe I have to do some manual process, and I'd happily do some googling, but I can't find anywhere to start on guidance
Thanks in advance, Steve C.