CODEWITHSUNDEEP
asp.netassembliesgacstrongname
Brad
Brad

Reputation: 1405

Strongly named assemblies in bin folder on ASP.NET 2.0

I know not to put strongly named assemblies into the bin folder on early versions of ASP.NET. I remember this caused problems, but I don't remember specifically what problems. Does anyone know if this still applies to ASP.NET 2.0? Is there any reason not to put strongly named assemblies into the bin folder on ASP.NET 2.0 or later versions?

Upvotes: 0

Views: 722

Answers (3)

Max Toro
Max Toro

Reputation: 28608

The problem you describe was fixed on .NET 2.0, so you don't need to worry about it anymore.

However, beware that if you put a strong-named assembly in the bin folder, and an assembly with the same strong name exists in the GAC, then the assembly in the GAC will get loaded.

Upvotes: 2

Shiv Kumar
Shiv Kumar

Reputation: 9799

There should be no problems with this. I've done it a few times during development/testing and I even have a site currently running that has strongly named assemblies in the bin folder with no issues.

Assemblies are strongly named for a reason (obviously) so you should have a good reason to drop them in the bin folder.

Upvotes: 1

Joel Etherton
Joel Etherton

Reputation: 37533

I have not experienced problems with strong named assemblies being put into the bin. I have experienced some Interop problems with strong named assemblies and versioning conflicts, but those were caused by developers compiling older versions of an ComPlus application library into the solution instead of the current or newer version.

Upvotes: 0

Related Questions