Prev: warning LNK4099: PDB 'mfcm80d.i386.pdb' was not found
Next: SetupDiGetDeviceInfoListDetail() buffer problem
From: Pieter on 13 Feb 2007 19:19
Ben wrote:
> How about moving all other headers in stdafx.h into a new pch.h which
> stdafx.h then includes before <new>? Then change your project properties
> to use pch.h as the precompiled header. Now all your source files get
> <new> and all your other headers, <new> isn't within the precompiled
> header, and you don't have to change each individual file.

We have hundreds of projects, I am looking for a solution that will require
a single change, e.g. the compiler environment or CRT / C++RT, i.e. one
global change instead one or more changes per project.

Regards
Pieter

"Ben Voigt" <rbv(a)nospam.nospam> wrote in message
news:%230IYlv7THHA.4684(a)TK2MSFTNGP04.phx.gbl...
>
> "Pieter" <alias(a)newsgroup.nospam> wrote in message
> news:F0DDCBFD-8538-4D8A-A3D0-E31BD9A26864(a)microsoft.com...
>> Charles
>>
>> Thank you for the feedback.
>>
>> All our projects have <new> in stdafx.h (this is from when VC7 would
>> choose between old behavior, return NULL, or new behavior, throw
>> std::bad_alloc, based on if <new> or <new.h> was included first).
>> Is there an alternative that does not require removing <new> from
>> stdafx.h?
>
> It sounds as if the issue is #include <new> from within the precompiled
> header.
>
> How about moving all other headers in stdafx.h into a new pch.h which
> stdafx.h then includes before <new>? Then change your project properties
> to use pch.h as the precompiled header. Now all your source files get
> <new> and all your other headers, <new> isn't within the precompiled
> header, and you don't have to change each individual file.
>
>>
>>
>> Regards
>> Pieter
>>
>> "Charles Wang[MSFT]" <changliw(a)online.microsoft.com> wrote in message
>> news:87Owek0THHA.2352(a)TK2MSFTNGHUB02.phx.gbl...
>>> Hi Pieter,
>>> I have reported this issue to the product team and they confirmed that
>>> this
>>> is a product issue and has been recorded.
>>> Now, they recommend that you remove the #include <new> from stdafx.h
>>> file.
>>>
>>> Also, I would like to know if this issue is critical to your project. If
>>> so, I recommend that you contact CSS for asking them to publish a hotfix
>>> for you.
>>> To obtain the phone numbers for specific technology request please take
>>> a
>>> look at the web site listed below.
>>> http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
>>>
>>> If you are outside the US please see http://support.microsoft.com for
>>> regional support phone numbers.
>>>
>>> If you have any other questions or concerns, please feel free to let me
>>> know.
>>> Have a good day!
>>>
>>> Charles Wang
>>> Microsoft Online Community Support
>>>
>>> ======================================================
>>> When responding to posts, please "Reply to Group" via
>>> your newsreader so that others may learn and benefit
>>> from this issue.
>>> ======================================================
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>> ======================================================
>>>
>>
>
>

From: Charles Wang[MSFT] on 13 Feb 2007 21:02
Hi Pieter,
I have tried some other ways such as using a wrapper header file, however
all of these methods did not work since if "#include <new>" was compiled,
the exports would be generated. The product team told me that the only way
is to remove the "#include <new>" from the stdafx.h file. They would like
to publish a hotfix if this issue is critical. That is why I recommend that
you contact CSS if you think that this is critical to your application. Via
CSS, you can ask them to publish a hotfix for you.
Appreciate your understanding on this.

Please feel free to let me know if you have any other questions or concerns.

Best regards,
Charles Wang
Microsoft Online Community Support



From: Pieter on 13 Feb 2007 23:50
Charles, thank you.
Do you have a case number I can refer to?

Regards
Pieter

"Charles Wang[MSFT]" <changliw(a)online.microsoft.com> wrote in message
news:7ae7lw9THHA.2352(a)TK2MSFTNGHUB02.phx.gbl...
> Hi Pieter,
> I have tried some other ways such as using a wrapper header file, however
> all of these methods did not work since if "#include <new>" was compiled,
> the exports would be generated. The product team told me that the only way
> is to remove the "#include <new>" from the stdafx.h file. They would like
> to publish a hotfix if this issue is critical. That is why I recommend
> that
> you contact CSS if you think that this is critical to your application.
> Via
> CSS, you can ask them to publish a hotfix for you.
> Appreciate your understanding on this.
>
> Please feel free to let me know if you have any other questions or
> concerns.
>
> Best regards,
> Charles Wang
> Microsoft Online Community Support
>
>
>

From: Charles Wang[MSFT] on 14 Feb 2007 06:58
Hi Pieter,
Did you mean the hotfix number? There is no hotfix now, but if it is
critical to you, you can ask CSS to publish a private hotfix only for you.
Actually they will ask the product team to publish the hotfix. If you
contact CSS, they will open a case for you. If I misunderstood your issue,
please feel free to let me know why you want to get a case number for
reference.

To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.

Best regards,
Charles Wang
Microsoft Online Community Support






From: Pieter on 14 Feb 2007 18:57
Charles, no I just meant if you have something like an internal case or
request number I can reference when we log the issue.


"Charles Wang[MSFT]" <changliw(a)online.microsoft.com> wrote in message
news:Q95zK%23CUHHA.2356(a)TK2MSFTNGHUB02.phx.gbl...
> Hi Pieter,
> Did you mean the hotfix number? There is no hotfix now, but if it is
> critical to you, you can ask CSS to publish a private hotfix only for you.
> Actually they will ask the product team to publish the hotfix. If you
> contact CSS, they will open a case for you. If I misunderstood your issue,
> please feel free to let me know why you want to get a case number for
> reference.
>
> To obtain the phone numbers for specific technology request please take a
> look at the web site listed below.
> http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
>
> If you are outside the US please see http://support.microsoft.com for
> regional support phone numbers.
>
> Best regards,
> Charles Wang
> Microsoft Online Community Support
>
>
>
>
>
>

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: warning LNK4099: PDB 'mfcm80d.i386.pdb' was not found
Next: SetupDiGetDeviceInfoListDetail() buffer problem