.Net
On one of the projects here the projectmembers were complaining about a really slow build of the solution in vs.net 2003.It happend only when logging on to the network. When they logon via a local account the solution builds just normal.After some googling i found this thread which lead me to the solution on msdnThe workstations of the project were logging on to a NT 4 server and are using a strong name key file in the projects of the solution.
Private keys generated are encrypted using a DPAPI master key.When a domain account is used,DPAPI makes two copies of each master key encrypting one with the user password and one with a domain secret. Encrypting the second copy requires calling over to one of the user's domain controllers. If this is an NT4 domain, then the DC doesn't support this operation. DPAPI won't give up though thinking that there must be a Win2K or better DC out there (that's perhaps just offline for a little while).DPAPI will continue to attempt to call over to the DC periodically perhaps every time a DPAPI call is made.After adding the following key (as the msdn article stated) to the registry the solution builds as fast as it should.
Write some code with VS.NET Beta 2 and the shareware starter kit. Read everything about this and the contest rules hereYou can win tickets for the PDC, hotel accomodations and 1000 Dollar for your fly voucher.
as one of the comments say: 'where is my keyboard?'