3

I'd like to use VolatileAssembly from the T4 Toolbox but do not want to require all developers to install the T4 Toolbox.

Is it possible include the DLL with with project in source control and reference it by path?

FishBasketGordo
  • 22,904
  • 4
  • 58
  • 91
Brian Low
  • 11,605
  • 4
  • 58
  • 63

1 Answers1

7

In Visual Studio 2010 you are able to do:

<#@ assembly name="$(ProjectDir)\external\SomeAssembly.dll"#>

Which I believe is what you are asking for.

EDIT: I understand VolatileAssembly is used to reference assemblies without locking them. This is one of the fixes for VS2010 SP1 so if your devs run VS2010 SP1 you shouldn't need VolatileAssembly anymore.

Just another metaprogrammer
  • 11,499
  • 2
  • 35
  • 54
  • Thanks @FuleSnabel. I tried adding this before the VolitileAssembly directive without success. The error is "A processor named 'T4Toolbox.VolitileAssemblyProcessor' could not be found for the directive named 'VolitileAssembly'. – Brian Low Aug 26 '11 at 17:09
  • Ahh I see, well it seems this is slightly more complicated than my initial assumption. Do you mind posting a template using the VolatileAssembly in a way similar to how you like to use. I could then experiment a bit. Also have you tried asking this question at: http://t4toolbox.codeplex.com/? – Just another metaprogrammer Aug 26 '11 at 17:42
  • Maybe this link on how to deploy custom directive processors can be of help: http://msdn.microsoft.com/en-us/library/cc138364.aspx – Just another metaprogrammer Aug 27 '11 at 06:24
  • Thanks, saw your edit. With VS2010 SP1 you no longer need VolitileAssembly from T4Toolbox. – Brian Low Aug 29 '11 at 19:34