Welcome Guest!

If you do not have an account yet on The Web Squeeze forums, please Register! It’s FREE and there are many benefits:

  • Receive Fast Advice
  • Learn Programming Languages
  • Get Professional Website Reviews
  • Quick Troubleshooting Assistance

> Assembly Probing

This is a discussion on Assembly Probing, within the ASP/.NET section. This forum and the thread "Assembly Probing" are both part of the Programming Your Website category.

 
Reply to this topicStart new topic
> Assembly Probing, how to limit?
Antti
post May 28 2008, 12:32 AM
Post #1


Rapid Squeezer
****

Group: Members
Posts: 235
Joined: 15-February 08
From: Finland
Member No.: 139



.NET framework has this "nice" feature called probing where it searches assemblies from various locations, including the /bin folder and loads them when the application starts. Is there a way to limit the assemblies that it loads? I've found out that it loads every file it finds, even if you rename the file extension to something else than dll. This would be usefull when updating assemblies with new ones so you could just rename the old one to assembly.dll.old and it would be ok. Currently this doesn't work.


--------------------
anttisimonen.com - .NET developer

anttis.wordpress.com - Blog
Go to the top of the page
 
+Quote Post
If you found The Web Squeeze to be helpful, please donate so we can keep this site FREE, FRESH, and fortified with Web Design & Development info!
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members: