> I stuck a copy of it up at http://freenetproject.org/snapshots/mfc70.zip (it > may need to be unzipped into the windows directory). This weekend I'll see > what i can do getting it to installer without actaully having everyone > downloading it every time they update.
I'm under the impression that Windows 2000, Windows ME and Windows XP regard MFCxx (and MSVCRT and MSVCPxx and MSVCIRT, etc) as system files which can only be installed (correctly) as part of the system service pack or hotfix procedure. It is not 1997 any more - you cannot just tell users to "unzip this Microsoft DLL into C:\Windows\System and see if that fixes the problem". I therefore also believe that releasing code built with MSVC7 will imply a dependency on the end-user installing either a very recent service pack OR the .net libraries. This is not a good situation. Either release the MSVC6 builds (almost all users will have the necessary MFC DLLs for that - Windows2000, ME and XP all install the necessary system files for MSVC6 releases anyway) or do static builds. > I hate microsoft, really i do. > I'm adding http://freenetproject.org/snapshots/msvcr70.zip . same directions > with this as mfc70.zip NO NO NO, it sounds more like you just don't understand them. Actually, what does redist.txt (installed with msvc7) say? (I genuinely don't know the answer to this, as I don't have msvc7, but I'll bet money it doesn't say "please distribute our dlls as .zip files and ask the end users to unzip them into the windows partition" anywhere) d _______________________________________________ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
