Re: VC++.NET2003/MFC target Win98 ?
From: Balboos (newsgroups_at_masonicbrother.com.No.Spam)
Date: 10/22/04
- Next message: Greg Locke: "win 98/xp bitmap backgrounds"
- Previous message: Rail Jon Rogut: "Re: CString is having problems concatenating"
- In reply to: Jim Howard: "Re: VC++.NET2003/MFC target Win98 ?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 22 Oct 2004 00:33:42 GMT
Jim:
Thanks a lot !
Balboos
Jim Howard wrote:
> "Balboos" <newsgroups@masonicbrother.com.No.Spam> wrote in message
> news:rhQdd.36380$YM4.12096257@news4.srv.hcvlny.cv.net...
>
>>Hi, all,
>>
>>I'm building an application (VC++/MFC) that may require execution on
>>Win98/ME/2000, etc, from inside VS.NET 2003. Originally, it was built
>>with VS6 using MFC, and was converted without much difficulty, to build
>>with VS.NET/MFC (unmanaged code).
>>
>>As the saying goes "WORKS GREAT ON MY PC" (XP Pro), but when I run it on a
>>Win98 system, it wants a specific .DLL, and this .DLL won't install.
>>
>>(1) Is it possible to set a switch in VS.NET to enable builds to run on
>>Win98? Perhaps the better question: where do I find the switch. I looked
>>around in all the sensible places, and either I didn't find it (or didn't
>>know it when I saw it).
>>
>>(2) Assuming there is such a switch: will that re-require the activation
>>of Enable3dControls(), which were flagged as depricated in the .NET build?
>>
>>Thanks, in advance.
>>
>>Balboos
>
>
> If you are using a wizard generated mfc application your stdafx.h will have
> code like this in it:
>
> // Modify the following defines if you have to target a platform prior to
> the ones specified below.
>
> // Refer to MSDN for the latest info on corresponding values for different
> platforms.
>
> #ifndef WINVER // Allow use of features specific to Windows 95 and Windows
> NT 4 or later.
>
> #define WINVER 0x0400 // Change this to the appropriate value to target
> Windows 98 and Windows 2000 or later.
>
> #endif
>
> #ifndef _WIN32_WINNT // Allow use of features specific to Windows NT 4 or
> later.
>
> #define _WIN32_WINNT 0x0400 // Change this to the appropriate value to
> target Windows 98 and Windows 2000 or later.
>
> #endif
>
> #ifndef _WIN32_WINDOWS // Allow use of features specific to Windows 98 or
> later.
>
> #define _WIN32_WINDOWS 0x0410 // Change this to the appropriate value to
> target Windows Me or later.
>
> #endif
>
> #ifndef _WIN32_IE // Allow use of features specific to IE 4.0 or later.
>
> #define _WIN32_IE 0x0400 // Change this to the appropriate value to target
> IE 5.0 or later.
>
> #endif
>
> You probably need to define WINVER approprate for your targets. It is
> certainly possible to write programs using Visual Studio .Net that use api's
> not supported on Win98.
>
>
>
> The other thing you can do is try remote debugging. It works very well with
> Visual Studio and isn't hard to set up. You can either copy the remote
> debugging components to your win98 target, or just share the remote
> debugging folder on your visual studio machine. As long as your app
> doesn't break the network connection it works great.
>
>
>
> Jim H
>
>
>
>
- Next message: Greg Locke: "win 98/xp bitmap backgrounds"
- Previous message: Rail Jon Rogut: "Re: CString is having problems concatenating"
- In reply to: Jim Howard: "Re: VC++.NET2003/MFC target Win98 ?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
