I've been using the "Create Private Assembly" function from the edit module definition screen since I discovered it yesterday, and it's way cool... HOWEVER, there is one slight problem I've discoverd.

If your stored procedures contain a plus sign "+", it is translated to a space by UTF7 encoding. And since UTF7 seems to be the default encoding scheme (see PAFile.vb, private function getTextEncodingType), you're kind of stuck, since the sproc gets copied over without the plus sign, and then refuses to create the sproc.

Any suggestions? I could mess with the base DNN product, but that doesn't seem very smart, but I can't imagine a different way to write the SQL. TIA.

Actually, the problem is ANSI encoding. If your file is encoded as ANSI (used by vs.net as it's default), then arithmetic operators are reserved characters. Open your script file in notepad, and do a "save as" and set the encoding to unicode.

Cathal