Problem with periods in output filenames

ladenedge · January 20, 2012 6:52AM

Hello. I'm having some trouble using SQL Packager with certain filenames in the /name: option - specifically those containing '.' and '-'. Here are some sample outcomes:

/name:upscript.R46535_to_5.0.441 (doesn't work)
/name:upscript.R46535_to_5_0_441 (works)
/name:upscript.R46535_to_5-0-441 (doesn't work)
/name:upscript-R46535_to_5_0_441 (doesn't work)
/name:upscript_R46535_to_5_0_441 (works)

Here's the error we're seeing:

Creating package...
Error: Error occurred whilst creating package 'upscript-R46535_to_5_0_441' in 'C:\TeamCity\buildAgent\work\33bce5bddfbed9dd\.': Compilation errors:
c:\Users\jay\AppData\Local\Temp\5\Red Gate\PEed66b3f9-04fe-4b57-8d6a-6ef3e95ff9e4.cs&#40;6,27&#41; : error CS1514: &#123; expected
&lt;repeated several times&gt;

We're also using the /scriptsource and /makeexe options, fwiw. Is there a workaround for this issue, or am I possibly doing something wrong?

Brian Donahue · January 23, 2012 6:23AM

Sorry to say, you can't have dots in the package filename. The reason for this is Packager uses the filename in the packager template as the .NET type name for the code, and a .NET type can't have dots in it, as they are used as separators.

Sorry for the inconvenience.

Problem with periods in output filenames

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk