Hi, I'm currently writing my own AuthenticationPackage but I don't think my work flow is optimal. I write it using Visual Studio 2008 and I use a virtual machine to test it. The problem is that I have to kill lsass.exe each time I want to upload a new version of my DLL on the virtual machine otherwise I can't upload it as the old DLL is used by the system. Once lsass.exe is killed I can perform de copy but then I have to wait for the system to reboot. To debug, I use kernel debugging or I use remote debugging from Visual Studio and I attach the lsass.exe process. How are you doing? Do you use a better work flow? Yannick
On Jul 10, 12:21 am, Yannick wrote: > Hi, > > I'm currently writing my own AuthenticationPackage but I don't think my > work flow is optimal. > > I write it using Visual Studio 2008 and I use a virtual machine to test > it. The problem is that I have to kill lsass.exe each time I want to > upload a new version of my DLL on the virtual machine otherwise I can't > upload it as the old DLL is used by the system. Once lsass.exe is killed > I can perform de copy but then I have to wait for the system to reboot. > > To debug, I use kernel debugging or I use remote debugging from Visual > Studio and I attach the lsass.exe process. > > How are you doing? Do you use a better work flow? > > Yannick That's pretty much the way it works. Why do you think it took 3 years to implement Kerberos in Windows? :) Dave
