"Object reference not set to an instance of an object"

[Kam]

Hi!

When I am trying to drag user controls or any controls from the Toolbox to a
form in some of my projects I get a dialog messages: (Microsoft Deployment
Environment)
"Object reference not set to an instance of an object"

Notes that:
1. It's a designer problem, not a reference problem. When I am adding this
user control directly to the code it works just fine, but I can't make it
work using the designer and see it in design time.
2. It happens only in some of the projects in the solution, not all of them.
3. In my company we are working with 'Microsoft visual source safe' and
other members of the team don't suffer
from the this problem.
4. Getting the latest version from 'source safe' didn't help.
5. Reinstalling VisualStudio .Net from scratch didn't help
6. When I am logging in as a different user the problem remains.

How can I restore the functionality of the designer to work with
(is it an environment problem)?

many thanks,
Kam

[guy]

when you say user controls if you mean custom built ones
and not ones that come with visual studio then...

remember that code actually runs at design time.

for example, when you drop a user control onto a form the
constructor code will be run.

if your machine is missing support libraries for the
offending control then these problems are bound to happen

-----Original Message-----
Hi!

When I am trying to drag user controls or any controls from the Toolbox to aform in some of my projects I get a dialog messages: (Microsoft DeploymentEnvironment)
"Object reference not set to an instance of an object"

Notes that:
1. It's a designer problem, not a reference problem. When I am adding thisuser control directly to the code it works just fine, but I can't make itwork using the designer and see it in design time.
2. It happens only in some of the projects in the solution, not all of them.3. In my company we are working with 'Microsoft visual source safe' andother members of the team don't suffer
from the this problem.
4. Getting the latest version from 'source safe' didn't help.5. Reinstalling VisualStudio .Net from scratch didn't help
6. When I am logging in as a different user the problem remains.
How can I restore the functionality of the designer to work with(is it an environment problem)?

many thanks,
Kam
.

[Kam]

it is both, the standard and non-standard controls.

[Kam]

it is both, the standard and non-standard controls.!!