-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I removed all the 'add' elements in the compilation/assemblies element.
So initially in my application's root web.config file:
<compilation debug="true" targetFramework="4.0">
<assemblies>
<add assembly="System.Web.Abstractions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
…
>>> More
-
as seen on ASP.net Weblogs
- Search for 'ASP.net Weblogs'
Something we've been doing in moq since the very beginning is to have a single assembly as output: Moq.dll. This reduces the clutter for users and lets them focus on what they need from our library, rather than getting the noise of whatever third-party (or internal) libraries we use to implement it…
>>> More
-
as seen on West-Wind
- Search for 'West-Wind'
When we work on typical day to day applications, it's easy to forget some of the core features of the .NET framework. For me personally it's been a long time since I've learned about some of the underlying CLR system level services even though I rely on them on a daily basis. I often think only about…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I have build 64-bit (x64) versions of some assemblies and am trying to obfuscate them with .NET Reactor, which claims to have 64-bit support. However, even if I disable all protection and locking options .NET Reactor is always producing 32-bit assemblies!
Does anyone know how to get .NET Reactor…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
Quite a few apps support plugins
Are there any downsides to having a large # of plugins ?
Is there a sweet spot beyond which there's a performance degradation perhaps ?
What's the largest # of assemblies you've seen loaded in an app ?
>>> More