Increment File and Product Version Number - Multiple IDE

• Download setup - 450.48 KB
• Download source - 339.19 KB

Introduction

This add-in replaces the add-in I provided a few years ago for use with Visual Studio 6. The previous add-in was based on an article by Mihai Filimon 'Increment Private Build Number'. This new add-in uses the core code of the previous add-in to increment the file and product versions in the rc and/or rc2 resource files. I have enhanced things slightly:

• Multi-IDE compatible. I have verified that it works in VC6, VC7.1 (VS2003), VC8 (VS2005) and VC9 (VS2008). I would imagine that it works for VC7.0 (VS2002). The installer registers the add-in for use by VC6, VC7.0, VC7.1, VC8, and VC9. It kind of works in VC9 although some users have reported problems:
1. If the VERSIONINFO block is in the .rc file, then VC9 reports that the resources have been changed externally, and do you wish to reload. Saying yes causes VC9 to crash. I have verified this, and very quickly moved my VERSIONINFO block(s) to the .rc2 file. I think this is a problem in VC9 and not my add-in :).
2. Manual increment works, but auto-increment does not — I have tested projects where the VERSIONINFO block is in the .rc2 file and it works for me. (This should now work because I have fixed the CBuildEventsSink class implementation of the EnvDTE::_dispBuildEvents interface.)

I would appreciate any feedback from users of VC7.0 as I have not tested it in this IDE.

• The file and product versions are made up of four groups of numbers — the major version, minor version, revision, and build number. (Some people may name these differently — but the concept is important here, not the naming convention. What's in a name, after all?) Anyway, the previous release of the add-in was restricted to incrementing the last number in this group. This new add-in allows you to choose which number to increment.
• Added the option to enable/disable the add-in.
• Added the option to only increment the version of the StartUp project. This is not applicable to VC6 as the add-in only increments the Active project anyway.
• Added the option to increment the version even if there were build errors. The default is to not increment.
• If you choose to increment the major version, minor version, or revision, you are given the option to 'reset' the lower numbers to their starting values. E.g., if you choose to increment the minor version, you may choose to reset the lower digits so that the revision is reset to 0 and the build number is reset to 1.
• If you have chosen to increment the major version, minor version, or revision, you may also choose, after one increment, to revert to auto-incrementing the build number.
• I have also added in the PrivateBuild and SpecialBuild entries of the version block, which will be incremented similar to the ProductVersion and FileVersion entries.
• I have added options to increment all or none of these four fields, or any combination in between.

Background

Having migrated from VC6 to VC8 (and now VC9), I was disappointed to see that my original IncVersion add-in, which had served me for nigh on 4 years, was not compatible with VC8. I tried to find a replacement, but none was really forthcoming, and suffered minor niggles etc. So, I decided to to code it myself.

I was very fortunate to stumble upon a most excellent article by sp1ff, Common Add-Ins. Great! Now, I could update my add-in and it will work in both my IDEs. After a bit of jiggery-pokery, I present to you my new, multi-IDE, slightly improved add-in. I say multi-IDE. I have obviously tried it on the two versions of Visual Studio that I have, VC6 and VC8. But due to the excellence of sp1ff's article, I have no doubt it will work for all versions in between. Unless I've messed up somewhere. (Note that most of the code is sp1ff's, and all his source files contain the required comment block to reflect this.)

Using the Add-In

Installation

I have included a setup.exe which, when run, will install the add-in DLL and its satellite UI DLL in a directory of your choosing. The second part of the install makes the required registry modifications to 'register' the add-in with VC6, VC7.0, VC7.1, VC8, and VC9.

Uninstallation will remove the DLLs and clean up the registry.

Incrementing

The add-in features a toolbar with two buttons. One to perform a manual version increment, the other to configure which number in the version group to increment.

IncVersion in VC6

IncVersion in VC8

Probably, more usefully, the selected version number is also automatically incremented every time the project/solution is built. For VC6, this is only the active project. For VC8, it is the active project with all its dependencies.

Note: When performing a manual increment using the toolbar Increment button, only the active project's version number is incremented. This is true for both VC6 and VC8.

Note: For both versions, the version number is incremented whether the source files have changed or not. Depending on the chosen option, if there are any errors in a project compile, the number which was incremented is reverted back to its original value.

Why increment first then if there were build errors? The increment function is called when the build is started and not when the build is completed, so that the new version number is compiled into the resulting object. Depending on the chosen option, any errors which may occur will cause the number to be decremented again.

This updated add-in parses the project file (.dsp/.vcproj) of the project(s) being incremented for all the .rc and .rc2 files it specifies. It is not therefore limited to .rc and .rc2 files having to reside in the project directory or its /res sub-directory. It will disregard any non-C++ projects not having the .dsp/.vcproj project filename extension.

Warnings

• If no resource files are found for a project, a warning message is displayed. This can be switched off, if desired.
• If doing a manual increment using the toolbar Increment button, a message box is displayed.
• If the increment occurs as part of a project compilation, the warning is written to the Output window of Visual Studio.
• For VC6, this is on the Macro tab of the Output window. For VC8, this is in the IncVersion pane of the Output window.
• A similar warning is displayed if one or more .rc/.rc2 files are found but none contain a VERSIONINFO block.

If the file or product version contains an asterisk character '*' in place of the number that is about to be incremented, the number is reset to 1 after IncVersion does its stuff.

IncVersion is able to increment multiple version blocks in both the .rc and .rc2 files at the same time (even if they are commented out!). And, there can be multiple language entries in a version block. All will be incremented.

The numbers in a version group are separated by a comma or a full-stop (a period in U.S. parlance). IncVersion is able to cope with one and/or the other in a single entry for file or product version, and can also cope with a mixture of these delimiters in the same group.

Thus:

VALUE "FileVersion", "4, 3, 1, 409\0"

VALUE "ProductVersion", "4. 3. 1. 409\0"

is okay.

VALUE "FileVersion", "4. 3, 1, 409\0"
VALUE "ProductVersion", "4. 3, 1. 409\0"

is okay too!

Finally, it doesn't matter about spaces between the digit groups, they are ignored. So FILEVERSION 4,3,1,409 is the same as FILEVERSION 4, 3,1 ,409.

Configuration

The add-in incrementing can be turned off by unchecking the 'Enable' checkbox.

By default incrementing is done if there were no builds errors. The option can be set to increment no matter what the build outcome by unchecking the 'Don't Increment If Build Errors' checkbox.

For VC7 onwards, you can choose to increment the version of all of the projects in the Active Configuration. Or to only increment the version of the StartUp project, check the 'Active/Startup Project Only' checkbox.

For all IDEs, you can select which version fields to increment — FileVersion, ProductVersion, PrivateBuild, and/or SpecialBuild.

You can change which number is incremented by clicking the Configuration button. A new dialog appears in VC6, the Options dialog appears in VC8.

Here, the add-in is enabled, all projects in the Active Configuration will be incremented, only projects with no build errors will be incremented, all four version fields are selected for incrementing, and the build number is selected for incrementing.

If a different digit is chosen, then you are presented with two more options.

Here, the VC6 add-in is configured to increment the major version once, and then to revert incrementing the build number. The VC8 add-in is configured to increment the minor version, resetting the revision (back to 0) and the build number (to start again at 1). It will also revert to incrementing the build number once the minor version has been incremented. It has also been configured to only increment the FileVersion and ProductVersion fields, and only the Active/Startup project.

Both IDEs have been configured to increment the version even if there were build errors in any of the projects.

If the 'Revert' check-box is left unticked, the add-in will continue to increment the last chosen digit. In our examples, the VC6 add-in would continue to increment the major version, and the VC8 add-in would continue to increment the minor version.

The last 'Display Warnings' check box determines whether or not a message is displayed (via a message box or to the Output window.) Untick it if you do not wish to see these warnings.

The Installer

This add-in is deployed using Jordan Russell's excellent Inno Setup. VC8 lacks a dedicated add-in deployment wizard, and I couldn't be bothered to work out what went where etc. So, I went for an approach I am very familiar with, and deployed the two DLLs using Inno setup. The second half of the install script then runs the various rgs files to register the add-in for the different IDEs. Uninstallation removes the DLLs and cleans up the registry. ;)

Request

Since I have not tested this on VC7.0, I would be very interested to know whether it does actually work in that IDE.

Of course, if you encounter any problems, then please post a message.

History

• 11 March 2008. New article submitted with IncVersion for VC6 and VC8 (tested on both).
• 18 March 2008. Updated article to reflect new requests/functionality.
• 19 March 2008. Updated to only increment C++ projects. Options to switch off warning messages.
• 28 March 2008. Fix for VC7 onwards to take account of the '>' character at the end of rc/rc2 filenames in vcproj files.
• 25 April 2008. Added incrementing of PrivateBuild and SpecialBuild. Added options to disable incrementing totally, to only increment the version of the Active/Startup Project (not relevant for VC6), and the ability to choose whether to increment FileVersion, ProductVersion, PrivateBuild, and/or SpecialBuild.
• 2 May 2008. VC8/9 Options - automatically selects the Increment Version Add-in options entry in IDE's Tools->Options dialog. VC8 and VC9 source code solutions. Sorry, no VC7/7.1. And, obviously, no VC6 (as this has VC7+ code in it which would not compile on VC6 anyway).
• 24 May 2008. Fixed issue for some users where the manual increment was working but the automatic increment was not. I would like to thank Josemi Antelo for helping me trace this issue. Added option to allow incrementing to be done even if there were project build errors.
• 10 June 2008. Fix to allow for spaces within project names. Thanks go to Kevanmc for pointing this out and providing the fix.
• 23 June 2008. Fixed uninstaller so that Toolbar is removed from various IDEs.
• 21 July 2008. Fixed VC6 install to puts dll’s in \Program Files\Microsoft Visual Studio\Common\MSDev98\AddIns directory. This should fix the problem with the two buttons not doing anything when pressed.
• 25 July 2008. Fixed VC6 (and probably all IDEs) to allow for multi-byte character project pathnames. My sincere thanks go to Haerim Lee for first identifying the problem and helping me to test a fix.
• 13 September 2008. Only increment for Build/RebuildAll events, not for Clean. Thanks to I'm Pear for finding this bug.
• 20 October 2008. Fixed situation where if you edit your resources in some way, compile and there are errors, the resource edits are lost. I have changed the internal logic so that version incrementing is done AFTER the project build has finished. Thanks again to Haerim Lee for finding this bug.

Outstanding Issues

What with trying to support so many IDEs all at once, and the more people make use of the add-in, the more minor (and some major!) bugs become apparent.

The following is a list of outstanding bugs that I am aware of, as well as any requested enhancements that I am considering/working on.

• Assembly file incrementing — for support for managed C++, C#, VB, and J#.
• Only increment version number if the source in a project has changed.
• Silence the .rc reload message. (Quite a popular one this, and I can understand why.)
• Only increment version number if the source in a project has changed.
• Increment all projects whose source has changed in a solution/workspace when doing command line build, or when clicking increment button — not just the active project like it does now — subject to the 'Active/Startup Project Only setting.
• Build configuration choices to decide whether to increment only debug or release, or any combination.
• SourceSafe integration - 'nuff said!

You must Sign In to use this message board.

FAQ    Noise Tolerance Very HighHighMediumLowVery Low   Layout Expand Posts & RepliesThread ViewNo JavascriptNo JS + Preview   Per page 102550

Msgs 1 to 25 of 135 (Total in Forum: 135) (Refresh) FirstPrevNext

Feature request: Install for all users M.Oerder 1:03 15 Jun '09   Thanks for this add-in. I have been searching for such an add-in for a long time. The problem is that I use a limited user account for normal work. The installer requires to be run under an administrator account and it registers the add-in only for this account. The result is that it is not available for all other users. Maybe this is the reason that some people don't see anything after the installation. It would be nice to have an option during setup to install for all users or if this is not possible generally install for all users. Thanks and best regards Sign In·View Thread·PermaLink Installing Problems VS 9 Member 5972325 7:43 12 Mar '09   Hi, I tried to install your PlugIn to Visual Studio 09 SP1. The installation progress was finished correctly, but I do not see anything, I can use (e.g. the shown toolbar). There is even no entry in the AddIn-Manager. Should I do something more to install it correctly? Thanks and best regards. Sign In·View Thread·PermaLink 1.00/5 (1 vote) How can I supress message "The file has been modified..." in VS9? Nikotin33 23:12 21 Jan '09   How can I supress message "The file has been modified outside of Visual Studio. Do you want to reload it?" in VS9? Option "Auto-load changes, if saved" have no effect!!! Sign In·View Thread·PermaLink Re: How can I supress message "The file has been modified..." in VS9? WH Tan 20:16 3 Feb '09   Hello Nikontin, I'm getting the same message as you. I think it has something to do with the issue reported by John. At the moment I'm getting around those issues by disabling the auto increment feature, and resolve to manual increment by using the increment version button on the toolbar. This probably not what you want. Whilst waiting for a new version, it's still better than having to edit all the fields in resource file manually. Best regards, WH Tan PS: I love this add-in. Hopefully we'll see an update soon. ______________________ WH Tan Sign In·View Thread·PermaLink Your solution and SourceSafe ? ? ? jtabakelis 6:16 13 Nov '08   Hello Mr. Walters, I have finally gotten your great addin project to work for me, but only when I pre-checkout of SourceSafe my RC2s. I do not us auto checkout in my vs2005 because I do not want to unknowingly add typos to any of my sources. I always have it prompt me to allow the check out to keep me safe. I also then keep my checked in files set to ReadOnly. I have found out that if I have a RC2 file checked out, the added in updates it as you have explained. It then appears that if the *.r* files are note writeable, then the addin skips processing them and these files do not appear in your error log leading me to believe that they were not being looked at from the *.vcproj file. What I was expecting was that the*.r* files that were not checked out, would prompt me to allow them to be checked out because that is my normal SourceSafe setting. When this did not happen, I assumed the addin was not working. If I set up the SourceSafe to auto checkout – then the my RC2 files do get automatically checked out and the addin updates them – but they never get checked back in unless I go looking for them. Yes, our true build machine is a separate machine from my development machine, and I could set its vs2005 to auto checkout and then manually check them all back in afterwards, but I was hoping to find a more automatable solution. Do you have any ideas? Thank You for your time, JT Sign In·View Thread·PermaLink Issues with VC6/VC9 Member 208192 8:39 4 Nov '08   It seems to update the version numbers after the build is done, or at least after the resource compiler has run. For example, after a build, my .rc (or .rc2) file has a version of "1,0,1,8", but the .exe and the .res have version numbers of "1,0,1,7". That also means the project is never up-to-date. So if I select "Build solution", it always does the resource compile/link steps. And if I try to debug, I get the message about the project not being up-to-date. I tried modifying the resources to make sure Visual Studio knew it had to run the resource compiler, but the version numbers were still out of sync. I've been testing it mostly in VC9, but I'm pretty sure it's doing the same thing in VC6. John Sign In·View Thread·PermaLink Re: Issues with VC6/VC9 Jordan Walters 9:22 4 Nov '08   Yep, you're right. I had a bit of a brain-freeze with the last release when I fixed the issue about the resource edits being lost if there were build errors. I am fixing this issue as well as getting VC6 to work properly so that dependent projects get updated too, and for all IDEs only those projects which have any code/resource changes. At the moment VC6 will update only the version in the active project, and does it all the time, regardless of any code changes. For all other IDEs the startup project and all its dependents have their version number updated even if there were no code changes. So you see I am trying to make things far more sensible - and hopefully this tim eI won't be half asleep when I do it! Sign In·View Thread·PermaLink 2.00/5 (1 vote) Does not find my RC & RC2 files to update . . . jtabakelis 5:49 29 Oct '08   My master solution (sln) contains multiple projects of DLLs, EXEs, and LIBs. Every project except the LIBs have their own RC2 file located in the RES direcory of that project. The project's .rc files reside in the projects root and the projects .vcproj files reference them as: RelativePath=".\jform80.rc" and RelativePath=".\RES\JForm80.RC2" The IncVersion messaging list that no VERSIONINFO block was found in the C:\$Src\Tws\SRC\DLL\jform\.\jform80.rc (which is understandable since this is in my RES rc2 file), but the messages never list that the RC2 file was ever checked. So I don't know it the RC fie was really checked either. I do not know if the \.\ is causing a problem with this or what. I could not rebuld tyour solution to debug it myself Thank You JT Sign In·View Thread·PermaLink Can not build your solution jtabakelis 5:36 29 Oct '08   I unzipped your attached source.zip, then started the IncVersion-VC8.sln in Visual Studio 2005. I then get a warning about missing JLogging and JLogging-VC8.vcproj. Ignoring all of these errors and trying to build the solution I then get errors on missing "IncVersion_AppNotAddin_VC8.h" I am trying to debug why your solution does not reckognize my .rc and .rc2 files in my .vcproj files (RelativePath=".\jform80.rc" and RelativePath=".\RES\JForm80.RC2") Sign In·View Thread·PermaLink Re: Can not build your solution Jordan Walters 12:37 29 Oct '08   Hiya, To debug the add-in you don't need the JLogging project, nor any of the test projects in the solution. All you'll need are IncVersion and IncVersionUI so you can delete the other projects from the solution. The latest version was posted to try to fix a problem where resource edits are lost if the build produced errors. I moved the increment code to the CBuildEventsSink::BuildProjConfFinish() event function. The only problem with this is that the newly incremented rc/rc2 file will not have been compiled into the build. So the increment needs to occur in the CBuildEventsSink::BeforeProjConfBuildStart() event handler. What I suspect you are seeing is that the rc2 file is indeed being updated, but it doesn't get compiled into the add-in until the next compilation. A bug which I am addressing. However that means the resource edits may be lost if there are other build errors. I am rejigging the code to cater for both situations. It's 'fairly' easy to design in for VC7+ IDEs, but VC6 is proving to be a pain. Sign In·View Thread·PermaLink Re: Can not build your solution jtabakelis 5:12 30 Oct '08   Thank you for your quick response. I will try removing the superfluous projects from the solution and retry again. As for my current rc/rc2 error and not updated messages, I do not believe that my RC2 is looked at because your error message lists the files it scanned, appearing to be *.rc* because I receive the following on all projects in my solution: Project: C:\$Src\Tws\SRC\DLL\jform\JForm80.vcproj No VERSIONINFO blocks could be found - no incrementing occurred. The following files were parsed: C:\$Src\Tws\SRC\DLL\jform\.\jform80.rch C:\$Src\Tws\SRC\DLL\jform\w220cm.rch C:\$Src\Tws\SRC\DLL\jform\.\jform80.rc And nowhere is my RC2 listed. When I look back at the RC2, I see it unchanged as it existed before. Because it does not look like it had been updated I expected that the true VERSIONINFO block was not found in it because it was not listed in the parsed list neither. I thought that SourceSafe might be preventeded it from being opened for update so I even checked out the RC2, cleaned the project and rebuilt it again. The RC2 remained physically unchanged. Thank You, JT Sign In·View Thread·PermaLink Re: Can not build your solution Jordan Walters 13:50 30 Oct '08   Is it possible that the rc2 file is not in the vcproj. Have a look in the IDE's solution explorer. If the rc2 file is listed in the Resource Files branch then there is a bug somewhere. If it's not then add the rc2 file to the project, save the project and try again. Jordan Sign In·View Thread·PermaLink Re: Can not build your solution jtabakelis 5:20 31 Oct '08   Thank you again for your quick response. The RC2 is in the vcproj. My vcproj contains the following: RelativePath=".\jform80.rch" RelativePath="w220cm.rch" RelativePath=".\jform80.rc" RelativePath=".\RES\JForm80.RC2" All my other projects in my solution have their own vcproj files in their respective subdirectories and are similar in their rc2 definition of RelativePath=".\RES\ProjectName.RC2" . . . Thank you for your help JT Sign In·View Thread·PermaLink Re: Can not build your solution jtabakelis 5:58 31 Oct '08   Hello, me again. I removed all the side projects from the IncVersion-VC8.sln, which took away all the loading errors. But now when I try to build the solution with only the IncVersion and IncVersionUI projects, the build stops imediately with the folowing missing file error: stdafx.h(83) : fatal error C1083: Cannot open include file: 'ObjModel\ADDAUTO.H': No such file or directory Thanks again for your help, JT Sign In·View Thread·PermaLink Re: Can not build your solution Jordan Walters 12:41 31 Oct '08   Ah, because my add-in supports VC6 (as well as VC7/8/9) it needs stuff from VC6. So you need VC6 installed as well. Sorry. I hope this doesn't cause you a problem. I will look into the rc2 problem - it used to work but there is a chance that I've broken it along the way. Jordan Sign In·View Thread·PermaLink Re: Can not build your solution jtabakelis 10:53 3 Nov '08   Sorry, I do not have access to VC6. Wee ent fro VC5 directly to Visual Studio 2005. . . Thank you, JT Sign In·View Thread·PermaLink Re: Can not build your solution jtabakelis 6:19 13 Nov '08   Mr Walters, I finally got a VC6 instalations set and have gotten your addin to build. Thank You. I have stared a new thead with what I have found out so I will stop this one here. JT Sign In·View Thread·PermaLink Is this the best approach? JeffBilkey 17:13 27 Oct '08   Jordan, I develop software, one package sold in over 20 countries, and I find the whole version number system ungainly. A series of numbers for a version is somewhat meaningless. My version numbers are Major, Minor, date (in astronomical format). For example the latest version is 2.71.081028. In other words version 2.71 with the build done in the year 08, month 10 and day 28. That way when I visit a customer and they have version 2.62.071028 I know at a glance it is exactly one year out of date. Sure this system relies on NOT doing more than one build per day, which if you are, I would suggest you have other problems! But even then, if you do more than one build per day, you could add a build number as well. However my system doesn't fit in with the standard version number system because the version number strips of the leading zero and anyway can't take a number greater than 32767. Hence I have abandoned the standard version number system. Has anyone else got a better idea? Any comments? Sign In·View Thread·PermaLink Re: Is this the best approach? Curtis J 18:51 29 Oct '08   What I'd do (now that I see your idea) is to store it in the VERSIONINFO like this: 2.7108.1029.156 Meaning version 2.71, built in 2008, October 29, and Subversion repository revision number 156. (I use an Subversion repository, and I wouldn't particularly care if the month loses the initial zero in the VERSIONINFO resource. I can always add it back in or do any other rearranging when my program displays it.) That'd be the way I'd split it up. As long as you updated the repository between builds, you could have more than one build per day, even! Sign In·View Thread·PermaLink Re: Is this the best approach? JeffBilkey 12:51 30 Oct '08   I didn't think of that because I sometimes add additional numbers after the 2.71. But I agree with you and will adopt it also. You just have to be consistent that no version gets greater than 99. As you say, if the leading zero is dropped off the third group, it is not a significant digit anyway. Thanks. Sign In·View Thread·PermaLink Some Issues with VC9 wmallory 7:54 22 Oct '08   Overall, very nice add-in. However, I ran into a few minor issues with VC9 you may want to know about. 1) Under VC9, the configuration dialog does not show the Display Warnings check-box. This may be due to my system also having VC6 installed. I was able to work around this by running VC6 and un-checking Display Warnings there. This then also turned off warnings for VC9. Another future improvement might be to add separate configuration info per VC version. Just a suggestion. 2) For VC9, looks like you clear the output box when you display your warnings, thus losing the previous build information. You might want to change that as well, or perhaps you're working to add a separate IncVersion output window for VC9 as well? That would be even better. 3) Under VC9, the active/start-up project gets its .rc updated, but another .rc in another project in the same solution space did not. Again, this might be because I have both VC6 and VC9 installed, but I'm not sure. Thanks for a very nice utility. Sign In·View Thread·PermaLink Re: Some Issues with VC9 Jordan Walters 12:47 29 Oct '08   Hello. 1. The Warning checkbox should appear for VC9 no matter what other IDE you have installed. I have seen similar problems occurring depending on the System's diaply Font dpi. The deafult is 96 which is what I run at. What is yours? 2. The warnings should be displayed in their own tab actually. If IncVersion needs to display any warnings if outputs the text to a new tab, then changes to make that tab visible. The 'Output' tab should still be populated with the results of the build. A few people complained about the IncVersion tab being selected, which is why I introduced the option to turn warnings off. 3. There are three possibilities here (4 if you think my add-in is at fault). a) You have got the option Active/Start up Project only ticked; b) IncVersion will only update rc's which are built as part of the Active project + its dependencies Build Process. So if your other project(s) are not dependencies of the Active Project (or one of its dependencies) the IDE will not build it. Hence I will not receive a project conf start event for that project; c) The project is unticked in the Configuration Manager dialog. (Build >> Configuration Manager...) Make sure the project that you think should be being built is ticked, and that it is ticked for the configuration you want, i.e. Debug, Release etc. Sign In·View Thread·PermaLink a bug~ I'm Pear 21:39 12 Sep '08   Hi,Jordan,You didn't check "BuildAction" before build start,so your kid still run when cleaning project/solution! p.s. I have no idea to make it work together with SourceControl.Did you find a good way? Pear modified on Tuesday, September 16, 2008 9:19 AM Sign In·View Thread·PermaLink Works, but... Hugh S. Myers 15:47 13 Aug '08   The addin works well, but the configuration button has no effect. Push and nothing happens--- no options dialog appears. Thinking that ritual magic might help, I copied the .dll to the addin directory, but alas no such luck. Since the default selections appear to be quite workable, I'm not in dire straits, but... --hsm p.s. this by the way for VC6 running in W2K with current service packs. Sign In·View Thread·PermaLink 3.00/5 (1 vote) Re: Works, but... Jordan Walters 2:14 14 Sep '08   I updated the installer for VC6 on 17th Aug. Try this new version. Sign In·View Thread·PermaLink

Last Visit: 16:46 23 Nov '09     Last Update: 16:46 23 Nov '09 123456 Next »