You could have all MapPoint calls proxied by your own server, which could safely hold the MapPoint stuff. You've got to handle authentication between the client and your own server, but at least you're not handing your MapPoint autentication details out to everybody.
So are we saying that MapPoint can't really be used in client applications? G. -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of Peter Foreman Sent: 13 May 2002 17:24 To: [EMAIL PROTECTED] Subject: Re: Hide part of code from Developers --- Peter Vertes <[EMAIL PROTECTED]> wrote: > How about storing the key on a remote server ? When you need it you > connect to it get it. Or extending on this idea; you could store the > key on a You could simply look for the code that gets it from the remote server and see what the return value is. > remote server, when you need to authenticate you call the > authentication code on the remote server side and have it spit back a > bool (true = user is authenticated / false = user need to try again). > I haven't actually implemented this but in theory it should work. Again someone could do the same. There is no real solution to hiding secrets in code. Only things that will make it harder to find. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
