Prev: warning LNK4099: PDB 'mfcm80d.i386.pdb' was not found
Next: SetupDiGetDeviceInfoListDetail() buffer problem
From: Pieter on 12 Feb 2007 17:40
Charles

We noticed the problem when we switched from VC 7.1 to VC8 SP1 and our
builds failed.
The linker fails when the EXE produces an import lib and the directory
specified for the import lib does not exist.
We can work around this problem by making sure the output directories are
pre-created.

I am just surprised that there are not more comments on this "bug", and I
wanted to ask around before we escalate the problem through premier support.


Regards
Pieter


"Charles Wang[MSFT]" <changliw(a)online.microsoft.com> wrote in message
news:NiCT4BoTHHA.2352(a)TK2MSFTNGHUB02.phx.gbl...
> Hi Alex,
> Per my understanding, you are concerned with the issue that the exports
> were produced when you put the "#include <new>" statement in the
> "stdafx.h"
> file however no exports when "#include <new>" was in the main CPP file.
> If I have misunderstood, please let me know.
>
> I reproduced your issue (actually VS8.0 without SP1 also has the same
> behavior), but I did not find any document regarding this topic. I will
> consult the product team to get the confirmation and let you know the
> response as soon as possible. The process may need a long time. Appreciate
> your patience.
>
> Also, could you please let me know why you want to prevent the exports if
> they did not impact your application?
>
> If you have any other questions or concerns, please feel free to let me
> know. It is my pleasure to be of assistance.
>
> Best regards,
> 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: Pieter on 12 Feb 2007 17:50
[Just correcting my managed newsgroup alias.]

"Pieter" <msnews(a)nospam.nospam> wrote in message
news:D89DE69F-8EC4-471F-95F1-8A64E50FEBD7(a)microsoft.com...
> Charles
>
> We noticed the problem when we switched from VC 7.1 to VC8 SP1 and our
> builds failed.
> The linker fails when the EXE produces an import lib and the directory
> specified for the import lib does not exist.
> We can work around this problem by making sure the output directories are
> pre-created.
>
> I am just surprised that there are not more comments on this "bug", and I
> wanted to ask around before we escalate the problem through premier
> support.
>
>
> Regards
> Pieter
>
>
> "Charles Wang[MSFT]" <changliw(a)online.microsoft.com> wrote in message
> news:NiCT4BoTHHA.2352(a)TK2MSFTNGHUB02.phx.gbl...
>> Hi Alex,
>> Per my understanding, you are concerned with the issue that the exports
>> were produced when you put the "#include <new>" statement in the
>> "stdafx.h"
>> file however no exports when "#include <new>" was in the main CPP file.
>> If I have misunderstood, please let me know.
>>
>> I reproduced your issue (actually VS8.0 without SP1 also has the same
>> behavior), but I did not find any document regarding this topic. I will
>> consult the product team to get the confirmation and let you know the
>> response as soon as possible. The process may need a long time.
>> Appreciate
>> your patience.
>>
>> Also, could you please let me know why you want to prevent the exports if
>> they did not impact your application?
>>
>> If you have any other questions or concerns, please feel free to let me
>> know. It is my pleasure to be of assistance.
>>
>> Best regards,
>> 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 03:29
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: Pieter on 13 Feb 2007 15:49
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?


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: Ben Voigt on 13 Feb 2007 17:13

"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.
>> ======================================================
>>
>


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