In a place far, far away, there was a project where the Architect decided on using embedded TSQL in a Dot Net application, rather than use stored procedures.

I located ILDASM.EXE (my Framework 3.5 version lives at C:\Program Files\Microsoft SDKs\Windows\v7.0A\bin on my home development PC) and created a shortcut to it in the SendTo folder. Now I could set about doing a simple demonstration to the Architect by taking one of the Dot Net EXE's with the embedded TSQL and sending it to ILDASM.  Since I had written most of the embedded TSQL, it was a matter of seconds before I located the embedded TSQL within the Exe. The TSQL that was supposed to be safely hidden within the EXE was easily located and and copied.

(It should also be noted that we could have encrypted the stored procedures on loading them to the database.)