RE: Corruption of temporary BAT files for Custom Build Steps (VC++)

[Gary Chang[MSFT]]

Hi Marius,

I have downloaded your sample project and reproduced the problem on my
side, it appears an issue in the VS.NET 2003 but I could not any similar
bug in out database.

Currently I will consult this issue with our product dev team members, and
update you as soon as possible.

Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

[Marius Storm-Olsen]

> I have downloaded your sample project and reproduced the problem on my
> side, it appears an issue in the VS.NET 2003 but I could not any similar
> bug in out database.
>
> Currently I will consult this issue with our product dev team members, and
> update you as soon as possible.

Hi Gary,

Excellent, could you also make sure that they check for the same problem
(but different bounds) in VS2002 and VS 2005, and which other bounds
create the same problem in all VS200*. I need to work around the issue
in our product nevertheless (and want to cover all problem areas, both
version and size wise), as we cannot depend on customers updating their VS.

Thanks!

Sincerely,
Marius Storm-Olsen

[Marius Storm-Olsen]

> I have downloaded your sample project and reproduced the problem on my
> side, it appears an issue in the VS.NET 2003 but I could not any
> similar bug in out database.
>
> Currently I will consult this issue with our product dev team members,
> and update you as soon as possible.

Hi Gary,

Some more details on the buffer overflow issue:

If a single line in the Custom Build Step buffer is over the lower
overflow bound (> 2085-#chars_expanded), and uses variable replacement
(/macros), it will always fail no matter how much "padding" is added
(for all versions of in front, after, over and under the line).
There is no workaround (as far as I know, except breaking up the line)
for this problem.

Sincerely,
Marius Storm-Olsen

[Gary Chang[MSFT]]

Hi Marius,

>Excellent, could you also make sure that they check for the same problem

>(but different bounds) in VS2002 and VS 2005, ...

I have tested your sample project with different length command line of the
Custom Buile Step(mostly larger) under VS.NET 2002 and VS.NET 2005(Beta2),
it builds well in these 2 IDEs.

Thanks!

[Gary Chang[MSFT]]

Hi Marius,

Currently we can confirm this is a new issue to the VS.NET 2003 IDE(not
occurs in VS2002 and VS2005), and we don't have a hotfix yet. If you have
more concern on this problem, we suggest you contact our Product Support
Services to get help on this issue, for a complete list of Microsoft
Product Support Services phone numbers, visit the following Microsoft Web
site:

http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS

In addition, as this problem is an product issue, PSS won't charge money.
Every MSDN subscriber has two free support
incidents. You could use one of them to contact Microsoft PSS. So you don't
need to pay money yet. Surely if the issue is a product issue, you still
have two free support incidents. :)

If you don't want to contact Microsoft PSS, you could submit product
feedback on
http://register.microsoft.com/mswish/suggestion.asp?&SD=GN&LN=EN-US&gssnb=1

If there is anything unclear, please feel free to post here. We are glad to
be of assistance.

[Gary Chang[MSFT]]

Hi Marius,

By the way, one workaround for VS.NET 2003 is to move some or all of the
custom build step into an external .bat file and invoke that from the
custom build step

Hope this helps!