[02/03] IE7 and ASP.NET warning

I downloaded and installed MS IE7 today, and after doing so, I couldn't run any ASP.NET applications in VS .NET 2003.

It would first warned me that the project I was opening was on an untrusted webserver, and asked if I wanted to open it or not. I simply said Yes and that seemed to take care of that.

When I went to run it, it said it couldn't start debugging due to security levels. I had to go into internet options in IE, and change the local intranet zone to include http://localhost

Now everything is working ok.

Not sure if this will happen to everyone, or if it had something to do with my existing settings, but just a heads up incase anyone runs into the same issue.

I've run into that problem with Windows 2003 as well. All about 'safe zones', but I've not understood why it needs to be so tightly integrated with Internet Explorer.

I guess perhaps because the VS IDE is launching IE but its hooked into it for debugging reasons?

If anything, MS should give you common scenarios for VS setups, and tell you what permissions should be in order to have things working.

IE7 also messed with regular winforms apps I have on a network drive and run daily.

Not only did it give me the "Publisher Not Verified" message when I ran them (even though these are exe's that were compiled right on my machine to the network, not downloaded) and also gave me .NET framework security errors.

I had to include the server that the share is on in my safe zone, and the problem went away.

But you do know that you can debug with Firefox too right?

I predict some sort of a learning curve with the release of IE 7 soon. We'll need to go over a re-learning of IE's security uhm... model.

Well it is no doubt IE7 is more secure than IE6, so perhaps that is why all of a sudden things seem broken, when it is maybe more like patching something that shouldn't have been going on in the first place.

Both problems were easy fixes.

I run both Firefox and IE on my machine, but I use IE for daily use.

99.9% of my customer base uses IE, so that is why I debug in IE when making ASP.NET apps.

The "added protection" firefox provides over IE6 isn't a major concern of mine, as I don't really visit shady sites and sure as hell don't go around installing activeX controls, etc...

I think IE7 also improved their CSS handling to be more "W3C" but we shall see if that proves true...

They have a INSTALLATION CHECKLIST. Don't know if it would be relevant to the issue you had. I didn't really delve into the details of it.

Yes,they have more CSS standards support now for IE 7. I am waiting to upgrade to 7 after a few weeksof letting everyone else find out the headaches withthe release version. :D

They are coming out with an optional block for the automatic updates to prevent it from automatically updating IE 6 to IE 7 without acknowledgement first some time in early November.