Search

InternalName should not include file extension by Herman2

Closed

1
0
Sign in
to vote
Type: Bug
ID: 778723
Opened: 2/7/2013 2:54:08 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
When creating a new version info block in the resource editor the InternalName value is set to the executable file name including the file extension. According to MSDN documentation the field should not include the file extension.

"Internal name of the file, if one exists?for example, a module name if the file is a dynamic-link library. If the file has no internal name, this string should be the original filename, without extension. This string is required."
(from http://msdn.microsoft.com/en-us/library/windows/desktop/aa381058(v=vs.85).aspx)
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

1. Open Visual Studio 2010 (did not test with 2012)
2. Open an executable file
3. Go to the version resource
4. Right click and select "New version info block"

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

English

Actual results

The field InternalName is initialized with "application.exe".

Expected results

The field InternalName should be initialized with "application".
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/8/2013 at 4:26 PM
Hello Herman,

Thank you for taking the time to provide your suggestion. After reviewing your reported issue in the context of all the issues reported to us, we have decided not to take any action on this feedback at this time.

Thank you,

Oleg Kharitonov,
Visual C++
Posted by Microsoft on 2/7/2013 at 8:35 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 2/7/2013 at 3:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.