Lunchtime Longhouse

work post – if you’re one of those folks that reads my blog for the pictures, just move along :)

I’ve got some code that compiles .resx files at run time, using them to make an in-memory resource dll assembly that I can use from a ResourceManager object. I take the RESX and convert it to a .resources file in the temp dir (which I get from Path.GetTempPath()), whose name is in a string var named resFileName.

There’s a bug in this code:

   1:    Dim vbCompiler As VBCodeProvider = New VBCodeProvider()
   2:    Dim codeParams As CompilerParameters = New CompilerParameters()
   3:  
   4:    codeParams.GenerateExecutable = False
   5:    codeParams.GenerateInMemory = True
   6:    codeParams.CompilerOptions = "/nostdlib /noconfig  /define:_MYTYPE=\""Empty\""  /resource:" & resFileName & "

If resFileName is a path containing spaces, our compile won’t go. On some systems, the temp path will contain spaces.

Here's how we get rid of it (see lines 6 & 7):

   1:    Dim vbCompiler As VBCodeProvider = New VBCodeProvider()
   2:    Dim codeParams As CompilerParameters = New CompilerParameters()
   3:  
   4:    codeParams.GenerateExecutable = False
   5:    codeParams.GenerateInMemory = True
   6:    codeParams.CompilerOptions = "/nostdlib /noconfig  /define:_MYTYPE=\""Empty\"""
   7:    codeParams.EmbeddedResources.Add(resFileName)

Simple once you know how. The moral of the story is never concatenate a filename into a string if you don’t have to.

Tags: programming, work

S	M	T	W	T	F	S
1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30

jeffpaulsen

getcher turnip onna stick