Code Access Security

In a project I am working on, one of the requirements was that the application be allowed to browse its own pages (e.g. programatically open up a web request and browse the html pages that are served up by the site).

Anyway, this permission is not allowed on the hosting environment they decided to use. This page talks about the permissions available in ASP.NET 2.0, and the different levels of security you can set on applications.

DLL Hell a possible solution (repost)

After making some newsgroup postings and researching a bit. I found out some info that might be a contributing factor to our problems with assemblies getting referenced correctly.

In our assemblyinfo file we are auto incrementing the AssemblyVersion . From my reading, this attribute is actually meant to BREAK combatibility. What we need to be using is the AssemblyFileVersion. This can be incremented w/o breaking compatibility and still help us figure out what DLL we are dealing with (which version).

This blog has an entry about it.

Note: I had to repost because I accidently used some tags in my article that don’t show up.

DLL Hell, a possible solution

After making some newsgroup postings and researching a bit. I found out some info that might be a contributing factor to our problems with assemblies getting referenced correctly.

In our assemblyinfo file we are auto incrementing the . From my reading, this attribute is actually meant to BREAK combatibility. What we need to be using is the This can be incremented w/o breaking compatibility and still help us figure out what DLL we are dealing with (which version).

This blog has an entry about it.