| Thread | Last Post | Replies |
|
| Force Rejit of a method | 30 Apr 2006 00:48 GMT | 5 |
Hello, Is there a way to force the ReJit of a method? One of the demos that I do in my 'Rooting the CLR' presentation is to do real time MSIL patching. The problem is that I need to apply the 'patches' before the JIT has
|
| Loadfrom different behviour on .net 2.0 versus 1.1 | 26 Apr 2006 16:40 GMT | 2 |
.net 1.1 -------------- Assembly called test.dll on c:\ and in gac. call Loadfrom("c:\test.dll") , always loads it from c:\
|
| CLR 2.0 | 24 Apr 2006 13:40 GMT | 5 |
I have a dll that I wrote in Visual Studio 2005 and would like to add it to one of our older apps (CLR 1.1). Can I do it? The machine has the .NET Framework 2.0 installed and the dll doesn't do anything special. It doesn't utilize Generics or anything..
|
| problem with namespaces in VB.Net (2.0) | 20 Apr 2006 18:45 GMT | 2 |
i have an aspx page in a web project, which loads a user control dynamically. (by the way i don't have any problems using namespaces in C# web projects, this seems to be just a VB thing).
|
| Constant unification - what's the best approach? | 19 Apr 2006 18:27 GMT | 1 |
I need a mechanism for unifying constant objects. Sort of like a generalization of String.Intern. The constants can be nested (think pure Lisp or immutable DOM).
|
| setting heap sizes | 19 Apr 2006 18:02 GMT | 1 |
In Java you can specify heap using ms mx options. My C# app is chrunring on GC and I was wondering if perhaps presizing the heap would improve performance. However I couldnt find any options for this. Is tehre a way to do this in machine.config or app.config ?
|
| can library compiled 1.0 be used in Application compiled in 2.0 | 18 Apr 2006 06:43 GMT | 4 |
I have an winform referencing another .net dll: I would like to ask if the following works: 1. Library built in VS.Net 2002, and referenced in a WinForm created in VS.Net 2005
|
| assemblyBinding redirection to an assembly when the public key tokens are different | 14 Apr 2006 10:24 GMT | 1 |
can you redirect in app.config to an assembly when the public tokens are different?
|
| which version clr will IE host by default? | 10 Apr 2006 22:17 GMT | 7 |
If IE load an assembly, I am wondering which version of clr IE will host? if we have both 1.1 and 2.0 at client side. Thanks
|
| Reference type size in heap | 09 Apr 2006 22:34 GMT | 2 |
Why does a reference type occupies 8 bytes in memory? I assume that 4 bytes are needed to identify the object's type (or for the virtual table), but what about the remaining 4 bytes? Second, why does the size of a structure that has only one byte in it, is
|
| Is it possible to run a console function and capture the result. | 09 Apr 2006 07:03 GMT | 1 |
I and not sure if this is the correct forum to post this queston. Any ideas will be appreciated. Need to call a base windows console command function (like dir or chkdsk) and capture the results for further processing.
|
| .net assembly optimizer? | 06 Apr 2006 00:13 GMT | 8 |
I know that managed c++ is faster than c# because the ilcode of a mc++ application is pre optimized. Would it then be possible to decompile a c# assembly as mc++ code and then recompile it with a managed c++ compiler, gaining more performance? Is there
|
| How to examine objects on Gen 2 heap? | 05 Apr 2006 12:57 GMT | 3 |
ENV: .Net 1.1, VS 2003, Windows Server 2003 SP1 We are seeing some issues with the Gen 2 heap unexpectledly increasing over a lengthy period in an ASP.Net application. To troubleshoot this we've been using the 1.1 CLR profiler, this shows allocations, but I am unable to find
|
| problem with file handles | 05 Apr 2006 10:46 GMT | 2 |
in my app i monitor the filesystem for changes with FileSystemWatchers. When the change is detected the app performs some actions using Shell32 to obtain information from the filesystem. now the problem is that apparently the CLR not always closes the file handles immediately.
|
| CLR version mismatch | 04 Apr 2006 15:11 GMT | 2 |
I have a managed application compiled on .net 1.1 calling a unmanaged ACtive X control which in turn uses a managed extension C++ COM dll compiled on . Net 2.0. This causes the following exception to be generated in the managed app
|