Are public functions and classes in App_code folder of a 'Website project' bad in ASP.net?
===

I have been working on an ASP.net project, and earlier, I had no clue about a 'Web site project' and a 'Web application project'. I thought both were the same, so I selected Web Site, and now I wish I had done elsewise to be able to use namespaces.

Anyway. now, I need to use some global functions and variables across all pages. So I figure the only way to do this is to make a class in the App_code directory and use its functions by instantiating an object where ever required. This is the only way out, right?

I noticed that I can only keep the class and its functions public, not even protected. I was just wondering if there's any security loophole in using a class that's public. Can anyone throw some color?

Thank you for the time.