Re: [DOTNET] ANN: QuickAdmin V1.1 - Maintenance interface builder

I think personal insults are way over the line I can see why DM wants to retire this list for more focused lists.. Demeanor for .NET - the premier .NET obfuscation utility http://www.wiseowl.com/Products/Products.aspx -Original Message- From: Thomas Tomiczek [mailto:[EMAIL PROTECTED

Re: [DOTNET] COM Interop calling a C# DLL from VB6

e assembly's version number, and by default, Visual Studio .NET projects are marked with a version of "1.0.*" (inside AssemblyVersionAttribute). This will cause your GUIDs to change on re-compile unless you change it to be a fixed version. Adam -----Original Message- From: Brent

Re: [DOTNET] COM Interop calling a C# DLL from VB6

ut from the > sample I just > >looked at, there is nothing in there at all about needing .SNK files. > > > >Patrick Burrows > >In this sinking board walk town > > > >Now Playing: no artist - audiotrack 11 (patcast) > >---

Re: [ADVANCED-DOTNET] Singleton pattern

An AppDomain is the managed equivalent of a process. Over time IIS will likely unload your AppDomain and start a new one. I don't recall how long IIS keeps an AppDomain around before it recycles it. The default may be forever. The settings are in machine.config though. -- Brent Rector, .NET Wise

Re: [DOTNET] Strongly named assemblies require Full Trust ???

That's not a way "around" the security model any more than booting to a DOS disk and running a program is, or installed a device driver. Sorry to be so blunt, but anyone that downloads an unknown .exe to his/her hard drive and runs it, is a fool. In my more cynical moments, I've occasionally tho

Re: [DOTNET] Strongly named assemblies require Full Trust ???

It was a patch that enabled this behavior. It is by design and will not be changing (at least for the foreseeable future). -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx -Original Message- From: franklin gray [mai

Re: [DOTNET] COM Interop calling a C# DLL from VB6

The docs are wrong when the claim a .NET assembly used via COM interop must have a strong name. As you state, they only need a strong name in order to be added to the GAC. As long as you understand the assembly search rules, you can use an assembly via COM interop (i.e. by a COM client) by placing

Re: [ADVANCED-DOTNET] singleton server problem

GC.SuppressFinalize doesn't keep an object from being garbage collected. The only way to prevent an object from being collected is to insure there is always a live reference to the object. -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/

Re: [DOTNET] Accessing struct properties

[inline] -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx -Original Message- From: Jim Arnold [mailto:[EMAIL PROTECTED]] Sent: Friday, May 24, 2002 10:00 AM To: [EMAIL PROTECTED] Subject: [DOTNET] Accessing struct

Re: [DOTNET] Specs

Kompella (847) 935-3692 >From: "Brent E. Rector" <[EMAIL PROTECTED]> > >There is no spec other than the Partition II metadata spec. Okay, >there are a few but none I've read so often. See section 22.2.7. > You can read messages from the DOTNET archive, unsubscrib

Re: [DOTNET] Does C# have equivalent of C++ const parameters/meth ods?

Marsh, Drew [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 22, 2002 4:46 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Does C# have equivalent of C++ const parameters/meth ods? Brent E. Rector [mailto:[EMAIL PROTECTED]] wrote: > Modifiers come in two flavors - required and optional. C

Re: [DOTNET] Does C# have equivalent of C++ const parameters/meth ods?

The runtime doesn't have the concept of const per se but it does have the more general concept of a modifier in a type signature. For example, "void Foo (const bar b)" in managed C++ actually generates a type signature that contains the VC++ const modifier applied to parameter bar. Modifiers come

Re: [DOTNET] Partition II Metadata Spec question

Get Serge's Inside Microsoft .NET IL Assembler book (ISBN 0-7356-1547-0). It's an excellent book and answers many of the questions I've posted here over the past few months. It's also much more readable than the partition II spec (the spec is pretty good though). Nowadays, I code from the spec but

Re: [DOTNET] Partition II Metadata Spec question

Owww! I've taken an arrow! Yikes! Another arrow! I'm hit. I'm down. But I'm still crawling forward... Yes, the Pioneer spirit strives onward -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx -Original Message- F

Re: [DOTNET] Object serialization to string representation

:17 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Object serialization to string representation inline with *** - Original Message - From: "Brent E. Rector" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, May 20, 2002 5:08 PM Subject: Re: [DOTNET] Object s

Re: [DOTNET] Object serialization to string representation

l Message ----- From: "Brent E. Rector" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, May 20, 2002 4:49 PM Subject: Re: [DOTNET] Object serialization to string representation IMO, the SoapFormatter is a better choice because it can represent all serializable .N

Re: [DOTNET] Object serialization to string representation

Obj = Me serializer.Serialize(writer, Obj) Dim s As String s = writer.ToString writer.Close() Return s End Function -Original Message- From: Brent E. Rector [mailto:[EMAIL PROTECTED]] Sent: Monday, May 20, 2002 4:35 PM To: [EMAIL PROTECTED

Re: [DOTNET] Object serialization to string representation

Well, you are using the "Binary" formatter to write the state of your object to the stream. But you subsequently try and read the binary data as a string. You'd have better luck using the SoapFormatter. -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.c

[DOTNET] Partition II Metadata Spec question

I cannot figure out how to use MethodImpl's to override a virtual method when I have multiple levels of inheritance using MethodImpl's. Let's start with a simple C# example: internal class Base { public override string ToString () { return "Base"; } } internal class Derived : Base { pu

Re: [DOTNET] BUG: Remoting does not distinguish methods differing only by return type

not distinguish methods differing only by return type The question is if this is a documentation bug or a CLR bug ... -- Henkk - Original Message ----- From: "Brent E. Rector" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, May 18, 2002 9:25 PM Sub

[DOTNET] BUG: Remoting does not distinguish methods differing only by return type

Remoting throws an ambiguous match exception when calling a method on a remote MBR object that differs from another method of the type only by the return type. Here's an example using pseudo-C# syntax: internal class AppDomainInfoFetcher : System.MarshalByRefObject { internal AppDomainInfo

[DOTNET] Runtime metadata and Reflection question

Remoting throws an ambiguous match exception when you call an overloaded method that differs from another only by return value. For example, int Foo (int a, double b); long Foo (int a, double b); The CLR seems to have no problem with this case. I've only seen the error while using Remoting so

Re: [DOTNET] Obscure .NET Deserialization bug

arth did you find this? I'd love to see the test case. Ted Neward {.NET || Java} Course Author & Instructor, DevelopMentor (http://www.develop.com) http://www.javageeks.com/tneward http://www.clrgeeks.com/tneward - Original Message - From: "Brent E. Rector" <[EMAIL

[DOTNET] Obscure .NET Deserialization bug

I doubt anyone else will run into this bug however I'm posting it for the archives. The CLR determines uniqueness of a member of a class using the name/signature tuple. That is, the CLR is perfectly happy encountering an 'int a' and a 'double a' in the same scope. Unfortunately, I found out last

Re: [DOTNET] Variant VAR type

.NET long is equivalent to Variant type VT_I8 - which is only support AFAIK on recent versions of COM automation, such as XP. -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx -Original Message- From: Mark A. Grego

[DOTNET] Not a Partition II metadata spec question

I forgot to change the subject line before... I was just asking because I've noticed (I think) slightly different behavior depending on whether the runtime is processing a compressed or uncompressed steam. For example, in a compressed stream, I wanted to logically delete a number of metadata tab

Re: [DOTNET] Partition II metadata spec question

I would, of course, fix up the PROPERTYMAP table appropriately... -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx -Original Message- From: Brent E. Rector Sent: Monday, May 13, 2002 8:48 AM To: [EMAIL PROTECTED

Re: [DOTNET] Partition II metadata spec question

Thanks again. One somewhat related question. In an uncompressed metadata stream (#-), are *PTR tables always required or only required when remapping is needed? For example, in an uncompressed metadata stream if I sort the PROPERTY table by Parent RID, can I then remove the PROPERTYPTR table? --

Re: [DOTNET] Hide part of code from Developers

The original requestor wants to hide a MapPoint login/key/something secret in an application so that people can't find it even though they have access to the application's binary(ies). There is no absolutely secure way of doing this. It all boils down to how hard do you want to make them work to

[DOTNET] Partition II metadata spec question

Re: the InterfaceImpl table. In the metadata, the interfaces implemented by a type consume a contiguous range in the InterfaceImpl table. That is, it's possible to specify the interfaces implemented by a type using a tuple consisting of the indices of first and last entries for the type in the In

Re: [DOTNET] Partition II metadata spec question

I suppose I should add that I understand that the ExportedType declarations for the nested types are used by the compiler when determining if a reference should be able to bind to the types. A better way to phrase my question is: Can there can be a cross-assembly/module direct reference (i.e. Nam

[DOTNET] Partition II metadata spec question

Given the following class declarations in the non-prime module of a multi-module assembly: public class Outer { public class Middle { public class Inner { } } } Given the following reference in an assembly that references the multi-module assembly containing the above declaration: c

Re: [DOTNET] SP1 and trusting an assembly?

This is just a guess but the effective security policy is the intersection of the policies for four different levels: Enterprise, Machine, User and AppDomain. This basically means that each level can only further restrict the effective policy established by the other levels. Maybe you're trying to

Re: [DOTNET] Serviced Components and New()

You don't have to create a new object but it will need to be initialized again. When your transaction commits/aborts, the COM+ runtime deactivates your object (basically either destroys or pools it). When you make a subsequent method call, the COM+ runtime automatically creates a "new" object (ei

Re: [DOTNET] .NET testing tools

Ahh, don't let anyone brow-beat you into not testing as you wish. Unit testing is simply a mechanism to help improve the quality of the software you write. It's but one tool. Anytime I've a method that's reasonably complex, I like to test it thoroughly in isolation while my understanding of it is

Re: [DOTNET] newbie question: How to read AssemblyTitle assembly attribute

// Get the running assembly Assembly a = Assembly.GetExecutingAssembly(); AssemblyTitleAttribute titleAttr = a.GetCustomAttributes (typeof (System.Reflection.AssemblyTitleAttribute), false)[0] as AssemblyTitleAttribute; -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfu

Re: [DOTNET] Windows .NET Framework, Japanese version

My daughter (who's 16) started learning Japanese three years ago. Now we get to watch and listen to lots of anime in the original language (whether we want to or not ). Maybe it's a growing trend in the U.S... -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wi

[DOTNET] Windows .NET Framework, Japanese version

For some reason, Windows Update keeps insisting that I should install the Windows .NET Framework, Japanese Version. This is in addition to and a separate download from the SP1 update. It's doing this on all my systems strangely. Anyone know what's up with it? -- Brent Rector, .NET Wise Owl Demean

Re: [DOTNET] Partition II Metadata Spec question

It difficult to obfuscate code with their obfuscator as it's not even available. Fortunately I don't need to attempt to write an obfuscator. I've already written one. Demeanor for .NET has processed hundreds of assemblies and is in use in production environments world-wide. Application level obfu

Re: [DOTNET] Partition II Metadata Spec question

Actually I'm working on application obfuscation (i.e. a closed set of assemblies) - for example, an EXE plus its set of private assemblies. I guess this is meta-obfuscation. I can obfuscate all public members as long as I chase down all references in the client assemblies and update them appropri

Re: [DOTNET] Partition II Metadata Spec question

I think my brain is now working for the day Never mind. -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx -Original Message- From: Brent E. Rector Sent: Friday, April 12, 2002 2:41 PM To: [EMAIL PROTECTED

Re: [DOTNET] Partition II Metadata Spec question

One last question (for the day ), am I correct in understanding that if I have a TYPEREF resolution scope of anything except 0 or 1, the decoded token will correctly reference the appropriate type? That is, there's no heuristic like the foreign typeref where I must compare namespaces and names and

Re: [DOTNET] Partition II Metadata Spec question

I knew that (at one time in the distant past it seems...) Thanks again. -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx -Original Message- From: Serge Lidin [mailto:[EMAIL PROTECTED]] Sent: Friday, April 12, 2002

Re: [DOTNET] Partition II Metadata Spec question

Ahh okay. There is a reference to the "COccManager" TYPEREF in a parameter to a global method (AfxEnableControlContainer ) but maybe at runtime AfxEnableControlContainer is never called. Method #154 --- MethodName: AfxEnableControlContainer (060

Re: [DOTNET] Partition II Metadata Spec question

pe 0 must be equivalent to 1 (this module). It's rather irregular, I agree, but then this whole business with zero resolution scope ("somewhere around here, go figure") is rather irregular. Thanks, Serge -Original Message- From: Brent E. Rector [mailto:[EMAIL PROTECTED]]

Re: [DOTNET] Partition II Metadata Spec question

r, I agree, but then this whole business with zero resolution scope ("somewhere around here, go figure") is rather irregular. Thanks, Serge -----Original Message- From: Brent E. Rector [mailto:[EMAIL PROTECTED]] Sent: Friday, April 12, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Re:

Re: [DOTNET] Partition II Metadata Spec question

ntor (http://www.develop.com) http://www.javageeks.com/tneward http://www.clrgeeks.com/tneward - Original Message - From: "Brent E. Rector" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, April 11, 2002 7:33 PM Subject: [DOTNET] Partition II Metadata Spec question &g

[DOTNET] Partition II Metadata Spec question

Using VS.NET, I created a MFC Application project. The *only* change I made was to switch on the /CLR command line option (which then forces you to turn a few others off). This produces a single module .EXE managed assembly containing with managed code and unmanaged data. PEVerify /MD states that

[DOTNET] Partition II Metadata II spec Errata

22.1.15 Element Types used in Signatures ELEMENT_TYPE_PTR0x0fFollowed by token ELEMENT_TYPE_BYREF 0x10Followed by token ELEMENT_TYPE_VALUETYPE 0x11Followed by token ELEMENT_TYPE_CLASS 0x12Followed by token ELEMENT_TYPE_CM