Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesSQL Parse errors when executing .SqlDataProviders during upgradesSQL Parse errors when executing .SqlDataProviders during upgrades
Previous
 
Next
New Post
1/12/2010 2:21 PM
 

OK, I'm confused.

We have created lots of custom modules without problems. Until now.

We've just recently packaged up some changes to modules and created scripts for upgrades to the database. In a few instances we are getting syntax errors when trying to run the scripts, even though the same scripts run fine in SSMS.

I'm beginning to wonder whether the issue is related to the plus symbol (+), because that seems to be a bit of a common theme. We are in the UK and therefore running en-GB and Windows 1252 (if that's relevant). When the syntax error is raised, looking in detail at the error message the + is missing from the script reported.

Has anyone else come across this, and come up with a solution?

I've just tried switching to en-US during installation and it seems to make no difference.

We're running 04.09.05 and have SQL2008 for our database server, in case of anyone else suffering this and a pattern emerging.

 
New Post
1/12/2010 2:36 PM
 

The SqlDataProvider files need to be saved as UTF-8 Format using notepad and Save As from the menu -if you're saving an ANSI encoding (which is the default within vs.net) , arithmetic symbols such as + and - will be stripped.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/12/2010 2:46 PM
 

Thanks Cathal, I appreciate the help. I'd never have guess that one.

To clarify, I assume you mean that DNN, or perhaps the Application Block, will strip them during processing, as the file saves correctly with the characters included.

Do you happen to know if an initial save in UTF-8 allows VS to recognise them as UTF-8 and will then preserve the encoding even when worked on in that environment? That would be a great help if it did, because it's only the very first time we create a file that we have to do anything different. Come on VS, help me out here!

Fingers crossed ...

 
New Post
1/13/2010 6:08 AM
 

To close off this topic, I can confirm that Visual Studio does respect (preserve) UTF-8 encoding. Opening a UTF-8 encoded .SqlDataProvider file, editing the content and saving it again retains the encoding and the file will be correctly handled by DotNetNuke during installation.

As detailed at http://unicode.org/faq/utf_bom.html, saving as UTF-8 in Notepad results in a Byte Order Mark of EF BB BF being appended to the start of the file (as well as the file characters being encoded according to the UTF-8 specification, obviously). Visual Studio knows how to interpret the mark and preserves it during edits, as well as carrying out the correct encoding on saving the file.

Copying 01.00.00 that is provided in the DotNetNuke Compiled Module template (jnstalled as part of the Visual Studio Installer package provided by DNN Corp as one of the package types at each release) is an alternative way of ensuring that your .SqlDataProvider file is correctly encoded, as this file is provided as a UTF-8 file.

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesSQL Parse errors when executing .SqlDataProviders during upgradesSQL Parse errors when executing .SqlDataProviders during upgrades


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out