I have made some pretty good headway with my complex App Updater Block needs, which I wrote about the other day here.
However I have run into a roadblock. One of the things I was trying to accomplish is actually doing authentication and authorization before the user even got the updates. I have a reason for this. However, I realize that now getting the user info to the new process that my stub application starts up is going to be a task which is not what I want to start hammering on. Although…maybe a combination of reflection and getcurrentprocess and then adding in a method to my main exe to pass an object in and then I can invoke that method and …and…and.. oh I’m too tired for this tonight! 🙂 I have used reflection with assemblies but never with a process, so I could just be on drugs with that idea.
.NET 2.0 ‘s version of the ProcessStartInfo class actually has username and password as well as LoadUserProfile (boolean) properties that will help me do this next year, but not now. And of course, we’ll have ClickOnce then anyway…
I will probably have to rethink my architecture again and another way to accomplish the result I was after that was the reason for putting the authentication right up front in the stub application.
Sign up for my newsletter so you don't miss my conference & Pluralsight course announcements!