VS IDE uses incorrect parameters for delay signing with TLBIMP

VS IDE uses incorrect parameters for delay signing with TLBIMP by Steve_Maillet

Closed

as Postponed Help for as Postponed

Type:	Bug
ID:	545024
Opened:	3/26/2010 4:23:51 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

When adding a COM reference to a project using delay signing the IDE generates the interop assembly using invlaid parmaters to TLBIMP resulting in an error and failure to build.

Details (expand)

English

Visual Studio 2010 Release Candidate

Windows 7

English

in VS2010 RC Create a .net V3.5 application (console or GUI shouldn't matter)
Add public key and set the application to use delay signing.

right click on the application project in solution explorer
Add a COM reference to a COM library (WUAPI Type library 2.0) [ I expect any other will fail but that was the one I found this on]

Get a yellow exclamation icon in the referecnes node of the product

try and build and you get errors in the output about TLBIMP

tlbimp is being called with the following parameters (edited to focus on key params)

/delaysign /keyfile:MyPublicKey.snk

NOTE: the use of the /Keyfile switch here. This is the bug!

/delaysign /publickey:MyPublicKey.snk

It should use /public key.

0 attachments

Posted by Microsoft on 4/13/2010 at 1:51 PM

Thanks for taking the time to send us the information about this issue.

This is indeed a bug and we will be working to fix this in a future release.

The only real work-around we have at this point is to use the Exec task to call TlbImp with the appropriate parameteres.

I am resolving as "Postponed", and we will look at for a future release.

Chuck England
Visual Studio Platform
Program Manager - MSBuild

Posted by Microsoft on 3/28/2010 at 11:20 PM

Thanks for your feedback.

We are routing 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 3/27/2010 at 4:10 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)