Question on VS.NET and VS6.0 Compatibility
-
I'm having trouble with my MFC applications. Recently I've moved my projects from using the old Visual Studio 6.0 to Visual Studio .NET. I've also changed my operating system from Windows 2000 to Windows XP. However, after I re-compiled and re-distributed my projects in Visual C++ .NET, I was informed by many of my clients that the applications will not open on their platforms (which they do not have Visual Studio installed). The errors being that there are several DLL files missing, including mfc70.dll and msvcr70.dll and a few others. I've tried to include those DLL files in the distribution packages, but that will increase the size of packages from less than 100K to over 1M. I've also tried to build my application using MFC in a static library instead of in a shared DLL. But that will still increase the size of my applications significantly. But even with the above solutions, there are still problems. While my applications open on my clients' platform, some of the functionalities are loss (for example, the CFileDialog class doesn't work anymore). This should be a common problem for many developers, I wonder if there's a better solution. Most of my clients are using Windows 2000 and Windows 98. Only a few of them are using Windows XP. Thank you to anyone who can give me some advice. J.
-
I'm having trouble with my MFC applications. Recently I've moved my projects from using the old Visual Studio 6.0 to Visual Studio .NET. I've also changed my operating system from Windows 2000 to Windows XP. However, after I re-compiled and re-distributed my projects in Visual C++ .NET, I was informed by many of my clients that the applications will not open on their platforms (which they do not have Visual Studio installed). The errors being that there are several DLL files missing, including mfc70.dll and msvcr70.dll and a few others. I've tried to include those DLL files in the distribution packages, but that will increase the size of packages from less than 100K to over 1M. I've also tried to build my application using MFC in a static library instead of in a shared DLL. But that will still increase the size of my applications significantly. But even with the above solutions, there are still problems. While my applications open on my clients' platform, some of the functionalities are loss (for example, the CFileDialog class doesn't work anymore). This should be a common problem for many developers, I wonder if there's a better solution. Most of my clients are using Windows 2000 and Windows 98. Only a few of them are using Windows XP. Thank you to anyone who can give me some advice. J.
these are just the problems we gladly accept, in order to use the latest goodies from MS. i always build with MFC statically linked, to avoid these kinds of problems. yes, it will increase the app size, but the app won't break when someone decides to change their version of the MFC DLLs. 1M really isn't that big. distributing a .Net app, now that's a big install package. but 1M will still fit on a floppy - no big deal. not sure about the CFileDIalog problem. i haven't seen that one yet. -c
Aiei i ea eio aoa i e eio e aigoa
-
these are just the problems we gladly accept, in order to use the latest goodies from MS. i always build with MFC statically linked, to avoid these kinds of problems. yes, it will increase the app size, but the app won't break when someone decides to change their version of the MFC DLLs. 1M really isn't that big. distributing a .Net app, now that's a big install package. but 1M will still fit on a floppy - no big deal. not sure about the CFileDIalog problem. i haven't seen that one yet. -c
Aiei i ea eio aoa i e eio e aigoa
I too am finding the same problems as "theorion16" I don't necessarily agree that we should put up with a 1MB distributable when we can do the same reliably with a 100K distributable. Especially if dealing with certain apps that are widely distributed via the net/email etc... I am in the process of finding a way to link a VC.NET app to older MFC DLL's. Will post results when found. Rick Eastes. ------------
-
I too am finding the same problems as "theorion16" I don't necessarily agree that we should put up with a 1MB distributable when we can do the same reliably with a 100K distributable. Especially if dealing with certain apps that are widely distributed via the net/email etc... I am in the process of finding a way to link a VC.NET app to older MFC DLL's. Will post results when found. Rick Eastes. ------------
RickEastes wrote: I am in the process of finding a way to link a VC.NET app to older MFC DLL's. i'd be totally shocked if that was possible. they've changed a lot of stuff in the new MFC (like CString). there are new interfaces etc.. but, if you do find a way, please be sure to write an article about it. :) -c
Aiei i ea eio aoa i e eio e aigoa