I have been working with custom install classes on .NET assemblies. Conveniently, they can be used to perform all manner of tasks through the use of the .net tool Installutil. When testing the ability to pass custom parameters (via the installutil.exe command line) I ran into a quirk:
It appears that parameters were being ignored if I passed them from an MSDOS console or batch file.
I knew this had to be a fluke, and finally stumbled on the answer: Order matters…or at least, put the assembly name last?
“c:\Windows\Microsoft.NET\Framework\v2.0.50727\installutil.exe Assembly.dll /Key=Value” will not work.
but…
“c:\Windows\Microsoft.NET\Framework\v2.0.50727\installutil.exe /Key=Value Assembly.dll” will ;)
0 comments:
Post a Comment