Re: Windows Impersonation in ASP.NET

Pierre posted an entry bout impersonation in ASP.NET szenarios. [Pierre]There are several scenario where you have to use the impersonation in ASP.NET. Consider, for example, you have to save and load files from a network share (file server). In that case, if the web site accept anonymous authentications, you have to impersonate a windows user who has enought privileges to access to that resource. You have three choices (I guess): Elevate the ASP.NET process identity - worse case since you could compromise the whole site security Impersonate a windows user during the single call ( Demand the task to a COM+ server application I think that the last is the best since we have more security and maintenance control[...] I agree with him that "Demand the task to a COM+ server application" is the best way of the three he listed. But for me impersonation it is still a don't. By the way i wanted to post this as a comment but "Comments on this post are closed". Yes this is some criticism on :-) ... So here my opinion as post in my blog: Avoid impersonation! If you need to "redirect a binary that is located on a different box than the webserver to the client" utilize another IIS on the 2nd machine or write a service that returns the binary data.  

What Video Game Character Are You?

I am a Defender-ship.I am fiercely protective of my friends and loved ones, and unforgiving of any who would hurt them. Speed and foresight are my strengths, at the cost of a little clumsiness. I'm most comfortable with a few friends, but sometimes particularly enjoy spending time in larger groups. (If I were not a Defender-ship you would be Pacman.)What Video Game Character Are You?

Back on the road

It's happening again. MichaelW and me are back on tour for TornadoCamp Xpress, the .NET 2.0 event of newtelligence. Today we started. We meet MichalK of Microsoft, he's a nice and smart guy, our local contact and I'm doing this post right in the middle of our C# 2.0 HOL. I miss my familiy @ home - love ya! cu soon. Cheers to the rest out there.

Uninstalling Previous Versions of Visual Studio 2005

If you have installed previous versions of Visual Studio 2005, such as Beta 1 or Community Technical Preview (CTP) builds of Visual Studio Team Suite, Visual Studio Standard or Visual Studio Professional, then you must uninstall the pre-Beta2 components in the exact order below before beginning to install any version of Visual Studio 2005 Beta 2. Go to the Control Panel and launch Add/Remove Programs Remove "Microsoft Visual Studio 2005 Professional" or other related IDE installs such as (Visual Studio Professional/Standard/Enterprise Architect/Team Suite, etc.) Remove "Microsoft SQL Server 2005 Express Edition" Remove "Microsoft SQL Server 2005 Tools Express Edition" Remove "Microsoft SQL Native Client" Remove "Microsoft Visual Studio 64bit Prerequisites Beta" Remove "Microsoft MSDN Express Library 2005 Beta" Remove "Microsoft Visual Studio Tools for Office System 2005 Runtime Beta" Remove "Microsoft Device Emulator 1.0 Beta" Remove "Microsoft .NET Compact Framework 2.0 Beta" Remove "Microsoft SQL Mobile 2005 Development Tools" Remove "Microsoft Visual J# Redistributable Package 2.0 Beta". If you receive an error message, see Note 1. Remove "Microsoft .NET Framework 2.0 Beta". If you receive an error message, see Note 2 Notes: If you see an error removing J# .NET Redistributable Package 2.0 from Add/Remove Programs, please run "msiexec /x {9046F10C-F5E7-4871-BED9-8288F19C70DF}" from a command line window If you see an error removing .NET Framework 2.0 from Add/Remove Programs, please run "msiexec /x {71F8EFBF-09AF-418D-91F1-52707CDFA274}" from a command line window