Re: Unsupported Functions and Objects w/ new SDKs from Visual Stud

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks for the help. For the time being I am continuing to use eVC++ 4.0.

When you were changing your include files and library paths were you
referencing to the new PPC 2003 SDK that comes with VS 2005 or an older
version?

"John Cramer [MSFT]" <JohnCramerMSFT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:E320158E-DC33-4D33-A2A6-BC5EF882E2FD@xxxxxxxxxxxxxxxx
> Hi,
>
> Sorry, when I first read your posting, I didn't realize that you wanted to
> use VS2005 to continue to support existing applications for older
> platforms.
>
> I got a PPC2003 application that was written on VC++4.0 and opened it in
> Visual Studio 2005, and it wasn't as easy as simply compiling it. It
> appeared
> that VS2005 did recognize the app as PPC2003, but it seemed to continue
> using
> the WM 5.0 include files and libraries. I was in the process of changing
> the
> solution properties to use paths to the right SDK, but ran out of time.
>
> I would suggest to you that you change the Directories selections for
> include files and libraries and see if that helps. I was starting to have
> some success with that but couldn't finish. In my opinion, you're correct
> that if it compiles with the SDK on an earlier development environment, it
> should compile in the newer one using the same SDK.
>
> I'm afraid that I will be out of the office for the next week, so I won't
> be
> able to get back to this until after the 28th. Regarding a list of what's
> changed between SDKs, I will ask around then and see what's available.
> --
> John Cramer
> SOFTWARE DEVELOPMENT ENGINEER, Mobile Developer eXperience Team
> Microsoft Corp.
>
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
>
> "mmobile" wrote:
>
>> Thanks for the reply.
>>
>> If you create a smart device application frim VS 2005 and include
>> AfxInet.h
>> you will get the following error because in AfxInet.h for the PC 2003 SDK
>> has the following lines:
>>
>> #ifdef _AFX_NO_INET_SUPPORT
>> #error Internet Services classes not supported in this library variant.
>> #endif
>>
>> You must have created a C++ MFC Desktop app.
>>
>> Also understand the new UI soft key support for WM 5 which we will have
>> in
>> our version of the application.
>> But I also want to use VS 2005 and compile PPC 2003 SE devices which do
>> not
>> have the soft keys. Why would the PPC 2003 SDK that comes with VS 2005
>> remove it if I am still coding for a PPC 2003 SE device?
>>
>> In particular I am looking for a document stating what has changed from
>> the
>> new PPC 2003 SDK compared to the old PPC 2003 SDK?
>>
>> Thanks again.
>>
>>
>> "John Cramer [MSFT]" <JohnCramerMSFT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message news:04C24A54-19A1-4DAA-B045-FD6E145A1FBE@xxxxxxxxxxxxxxxx
>> > AfxParseURL is still there. Just to be sure, I created a VS 2005 C++
>> > MFC
>> > app,
>> > called the API, and it all compiled just fine. Make sure to include
>> > AFXINET.H.
>> >
>> > You're right, wce_AsciiToWide is no longer there but you shouldn't have
>> > any
>> > trouble replacing it with code of your own. It's simply a character by
>> > character copy from the ASCII string to the wide string with a wchar_t
>> > cast
>> > to make the compiler happy.
>> >
>> > CCeCommandBar is no longer supported because of the UI design change in
>> > WM
>> > 5.0. The CommandBar has been replaced by soft keys which can be set up
>> > as
>> > buttons or menus. If you are porting your application to WM5.0, you
>> > should
>> > replace the CommandBar in your app with softkeys to make it compatible
>> > with
>> > the new UI and functionality. Otherwise, your app will look out of date
>> > and
>> > will be awkward to use compared to those other apps that did upgrade
>> > and
>> > more
>> > easily support one-handed operation.
>> >
>> > --
>> > John Cramer
>> > SOFTWARE DEVELOPMENT ENGINEER, Mobile Developer eXperience Team
>> > Microsoft Corp.
>> >
>> >
>> > This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >
>> >
>> >
>> >
>> > "mmobile" wrote:
>> >
>> >> I recently installed Visual Studio 2005 and have been trying to
>> >> compile
>> >> my
>> >> old eVC++ 4.0 application. Thus far I have found that the following 2
>> >> functions are not available: "AfxParseURL" and "wce_AsciiToWide".
>> >> Also I
>> >> can't find CCeCommandBar. Does anyone know the equivalent functions
>> >> and/or
>> >> objects I should use?
>> >>
>> >> Does microsoft have a document of what has been removed from the
>> >> latest
>> >> PPC2003 SDK that comes with VS 2005? I was using eVC++ 4.0 with the
>> >> PPC
>> >> 2003 SDK (v 04.20.000)
>> >>
>> >>
>> >>
>> >>
>> >>
>>
>>
>>


.

Quantcast