Search

VS 2012 is unable to locate envdte.dll from T4 template file by Tobi_B

Closed
as By Design Help for as By Design

1
0
Sign in
to vote
Type: Bug
ID: 776194
Opened: 1/9/2013 10:58:39 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
We are currently evaluating the upgrade from VS 2010 to VS 2012 as we require features from .Net framework 4.5. During this evaluation I just stumbled upon the issue that VS 2012 is unable to locate the envdte.dll from within a T4 template file.

This will fail:
<#@ Assembly Name="envdte.dll" #>
with the error: Compiling transformation: Metadatafile 'envdte.dll' could not be found

To resolve the issue we currently have to specify the full path to the envdte.dll so this will work:
<#@ Assembly Name="C:\Program Files (x86)\Common Files\microsoft shared\MSEnv\PublicAssemblies\envdte.dll" #>

Although a possible workaround is available, it should not be necessary to specify the full path to the dll and should, in my opinion, be considered a bug and treated as such.

Kind regards,

Tobias
Details (expand)

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

Visual Studio 2012

Steps to reproduce

Reference envdte.dll from within a t4 template file.

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

German

Actual results

envdte.dll can not be found

Expected results

VS 2012 should behave like VS 2010 in this point and envdte.dll should be found by VS 2012.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 1/25/2013 at 11:46 AM
Thanks for you feedback. To make this work remove the .dll from envdte. When you specify the extension, T4 thinks you want a fully qualified path. If you change your attribute to <#@ assembly name="envdte" #>, it will work.
Posted by Microsoft on 1/15/2013 at 1:15 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 1/9/2013 at 11:15 PM
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.