by admin on Tue Dec 09, 2008 3:17 am
That's a bit odd.... that should only occur if you turned on the "EncryptConnectString" property. Which application did this occur on?
Using this EncryptConnectString feature is somewhat of a "catch 22"... you need to be able to encode the connection string so you can put it in the app.config file. So, I created the ConfigureSOSOS utility just for that purpose.... it will allow you to write to the encoded connection string to the app.config file. So, just compile and run the ConfigureSOSOS utiltiy, select the application to configure, and then point to the app.config file that's inside the directory structure of the source code. (Normally you'd use this utility on the *.exe.config file after compiling, but in this case, you need it for the app.config file so you can do debugging)
After changes are made in this manner, when you first restart the solution, Visual Studio will detect that changes have been made to the app.config file "outside" of Visual Studio. It will ask if you want to accept those changes (not in those exact words), so just answer "yes", and you'll by on your way.
Yes, you'll have to do this for each of the app.config files in each of the SOSOS suite's directory structure (typically 4 of them... SOSOS, RunSOSOS, PollSOSOS, and ViewSOSOS)