Done yesterday

G'day

A technique I use when I'm trying to set up a lookup on an enum, is to create a variable of the enum type, then get the type of the variable, and the AssemblyQualifiedName of the type, e.g.

Usually I do this in the debugger, put a breakpoint on the Msgbox line, put fred.GetType.AssemblyQualifiedName in the Watch and copy the literal value from the Watch to where I want the enum name. Especially useful wher it isn't your enum that you're trying to use.

Hope this helps. I also reccomend all the enums in one class.

Peter

Glad you found your issue.  The only time that you will generally have an issue with the VS DTE not "seeing" an enum when you know with all of your being that it should is when the AppDomain of the DTE is holding on to an older version of an assembly and will not load the newly built assembly housing the enum.  This is common if the assembly is stored in the GAC and from time to time VS just doesn't want to let go for unknown reasons.  But at any rate, it looks as though you were already on top of it

That is on my list. So far, I have only 2 enums in the project, so it will not be too hard to refactor this later after I have wowwed the client with how quick I am

I second Edhy's suggestion about placing the enums in a separate class file.  Glad you got it going!

Hi Marcia,

1. Exit VS and open the solution again and re-build, then see if it works. 
2. If not, try creating the Enum in a separate class file, re-build, then assign the enum to the combobox again and test.

Edhy Rijo

OK - Got it solved. The enum was defined in the wrong place and that is why the framework couldn't see it.

Thanks for trying to help.

OK - I stepped thru the code in Combobox.Requery() and I am seeing that this line in the GetReferencedAssemblies() method:

'-- Try to just get the type before moving on

loType = Type.GetType(TypeName, False, True)

returns null.

It seems that it cannot find the enum. What would cause this?

No - still no items in the list

Try changing:

to

Any difference?