One or more of the types in the assembly unable to load

[Tolga Erdogus]

Hi,

out of the blue, I started getting errors when trying to open a form that I
have built in VS.Net 2003. The error is regarding an Activex control.
After further investigation, it turns out that I am getting the following
error anytime a drop an ActiveX control on a winform: "One or more of the
types in the assembly unable to load", which is the cause of my form not
opening.

This happens with ANY Activex even though the ActiveX is probably registered
and works at run-time with previously compiled applications. This seems to
be a design-time problem only.

I recently installed a few new software development tools/products, but I
have uninstalled them now to see if it fixes the problem - it doesn't.

Anybody seen this before?

Thanks

[Tolga Erdogus]

I uninstalled absoultely everything that I installed in the last few weeks.
Then I unsintalled VS.NET 2003, reinstalled the prerequisites and
reinstalled VS.NET.

Still get the same errors. The only thing I can think of is that one of the
tools I uninstalled came with a prerequisite installation for those who
don't have vb6. That installed a bunch of dlls in to the system directory
and it doesn't have an uninstall.

"Tolga Erdogus" <to**********@alum.mit.edu> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

Hi,

out of the blue, I started getting errors when trying to open a form that I have built in VS.Net 2003. The error is regarding an Activex control.
After further investigation, it turns out that I am getting the following
error anytime a drop an ActiveX control on a winform: "One or more of the
types in the assembly unable to load", which is the cause of my form not
opening.

This happens with ANY Activex even though the ActiveX is probably registered and works at run-time with previously compiled applications. This seems to be a design-time problem only.

I recently installed a few new software development tools/products, but I
have uninstalled them now to see if it fixes the problem - it doesn't.

Anybody seen this before?

Thanks

[Kevin Yu [MSFT]]

Hi Tolga,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that when you are adding an ActiveX control
to a windows form in VS.NET 2003 designer, an error "One or more of the
types in the assembly unable to load". If there is any misunderstanding,
please feel free to let me know.

As far as I know, this might be a security problem. You can try to get it
work by adjusting
(to get there... Control Panel - Microsoft .NET Framework 1.1 Wizards -
Adjust .NET Security - Make changes to this computer - Local Intranet)

I also found out that it works ok if your disconnected from the network.

This means that the Visual Studio is trying to read a file from the network
that it really doesn't need since the network doesn't have to be connected
for it to work correctly. Some kind of intermittant bug with the studio
since only a very select group have reported this problem.

If anything is unclear, please feel free to reply to the post.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[Kevin Yu [MSFT]]

Hi Tolga,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that when you are adding an ActiveX control
to a windows form in VS.NET 2003 designer, an error "One or more of the
types in the assembly unable to load". If there is any misunderstanding,
please feel free to let me know.

As far as I know, this might be a security problem. You can try to get it
work by running the .NET Framework 1.1
Wizard. Here are the steps:

1. Start -> Controls Panel -> Administrative Tools.
2. Start Microsoft .NET Framework 1.1 Wizards.
3. Click Adjust .NET Security -> Make changes to this computer.
4. Set the level of trust of Local Intranet to full trust.

I think the ActiveX control might be querying for some resources from the
network, so that the error is generated.

HTH.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[Tolga Erdogus]

Kevin,

your description of my problem is correct, except that this does not happen
with one particular ActiveX, but with ANY one that I try.
I tried your suggestion, but I get the same problem.

Thanks

"Kevin Yu [MSFT]" <v-****@online.microsoft.com> wrote in message
news:sm**************@cpmsftngxa10.phx.gbl...

Hi Tolga,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that when you are adding an ActiveX control
to a windows form in VS.NET 2003 designer, an error "One or more of the
types in the assembly unable to load". If there is any misunderstanding,
please feel free to let me know.

As far as I know, this might be a security problem. You can try to get it
work by running the .NET Framework 1.1
Wizard. Here are the steps:

1. Start -> Controls Panel -> Administrative Tools.
2. Start Microsoft .NET Framework 1.1 Wizards.
3. Click Adjust .NET Security -> Make changes to this computer.
4. Set the level of trust of Local Intranet to full trust.

I think the ActiveX control might be querying for some resources from the
network, so that the error is generated.

HTH.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[Nick Malik]

The apps that you installed, did they include bits of the framework (not the
whole thing, just bits of it?) That could cause some problems.
Also, when you uninstalled VS, did you clear the GAC and uninstall the
framework?

It sounds like someone has added their own code to a GAC component or a
Framework component (possibly with malicious intent).

--- Nick

"Tolga Erdogus" <to**********@alum.mit.edu> wrote in message
news:ea**************@TK2MSFTNGP10.phx.gbl...

I uninstalled absoultely everything that I installed in the last few weeks. Then I unsintalled VS.NET 2003, reinstalled the prerequisites and
reinstalled VS.NET.

Still get the same errors. The only thing I can think of is that one of the tools I uninstalled came with a prerequisite installation for those who
don't have vb6. That installed a bunch of dlls in to the system directory
and it doesn't have an uninstall.

"Tolga Erdogus" <to**********@alum.mit.edu> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

Hi,

out of the blue, I started getting errors when trying to open a form that

I

have built in VS.Net 2003. The error is regarding an Activex control.
After further investigation, it turns out that I am getting the

following error anytime a drop an ActiveX control on a winform: "One or more of the types in the assembly unable to load", which is the cause of my form not
opening.

This happens with ANY Activex even though the ActiveX is probably

registered

and works at run-time with previously compiled applications. This seems

to

be a design-time problem only.

I recently installed a few new software development tools/products, but I have uninstalled them now to see if it fixes the problem - it doesn't.

Anybody seen this before?

Thanks

[Tolga Erdogus]

I uninstalled the framework, but I didn't delete the assembly directory.
It still doesn't work...

[Tolga Erdogus]

Three days of frustration later, here is the solution:

Blow away the C:\Documents and Settings\$username$\Application
Data\Microsoft\VisualStudio\7.1 directory
and restart VS.NET 2003.
"Tolga Erdogus" <to**********@alum.mit.edu> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

I uninstalled the framework, but I didn't delete the assembly directory.
It still doesn't work...

[Kevin Yu [MSFT]]

Hi Tolga,

It was nice hear that you have found a solution. Thanks for sharing your
experience with all the people here. If you have any questions, please feel
free to post them in the community.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[Tolga Erdogus]

No problem. Actually, I am not sure if it is the solution that I wrote in
my previous post or logging in to the computer as "administrator", launching
VS.NET 2003 once, logging off, logging as yourself and then launching VS.NET
2003 that fixed it.

I believe it is one or the other (or a combination of both) that fixed my
problem.

"Kevin Yu [MSFT]" <v-****@online.microsoft.com> wrote in message
news:3Y*************@cpmsftngxa10.phx.gbl...

Hi Tolga,

It was nice hear that you have found a solution. Thanks for sharing your
experience with all the people here. If you have any questions, please feel free to post them in the community.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."