Why bother having a resume? via Sorry, folks, you still need a resume
If you’re really good, you don’t need a resume. The only reason I have one is because occasionally someone ASK me for one specifically. Gotta have something to hand them. But, I can honestly say I have not used a resume to get a contract in at least 5 years and probably only handed one out 3 times in the last 10 years.
If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
Yesterday, we looked at how to setup the web.config file and modify the business logic layer to make use of Profile properties to give us unique SQL logins when we use the SqlMembership provider for forms authentication. Today, we are going to show you the code you will need to associate the profile properties with the user.
There are cases where it is advantageous to have a separate sql login for each user login who will be editing your database. If you are using Windows authentication, this is not a problem because you can pass the windows authentication tokens on through to the db without having to do a whole lot of work.
But, what about times where setting up a separate windows user for each person who will be accessing the system is more work than it’s worth, or as is the case in shared hosting plans, just isn’t practical?
So far, I’ve seen:
