Hi there, I had noticed the same thing. What it boils down to is that every time that Visual Studio builds the solution, Sage thinks it's a new program. If you run your executable from you bin folder after you have given permissions, SAGE will not ask for permissions again. 

Thank you! Let me try it with the exe. I will confirm.

Yes, Sage 50 takes application evidence, so every time you change the .exe, you'll have to re-authenticate. 

This is a security measure to ensure that someone doesn't modify an authenticated application to attempt to gain access. 

I agree that it is a bit of a pain during the development process.