day0ops
day0ops

Reputation: 7492

Value cannot be null

VS 2010 is reporting this warning "Value cannot be null". However, the project seems to be compiling fine. It doesn't show any other information that shows why this happening. I'm developing a project to run on Microsoft Robotics Studio.

Description: "Value cannot be null"

File: ** dssproxy

How can I find more information regarding this warning ?

The code is 3000+ lines. So I'm not sure if its worth posting here.

enter image description here

Thanks in advance.

Upvotes: 4

Views: 1716

Answers (2)

day0ops
day0ops

Reputation: 7492

Thanks for all the suggestions.

In the end it was a missing namespace on one of the files i have added as a Link. Perhaps why dssproxy.exe was complaining. Wasn't very obvious by "Value cannot be null" though.

Wouldn't have been able to figure it out had I not started from scratch :(.

Thanks again.

Upvotes: 2

Dor Cohen
Dor Cohen

Reputation: 17090

The issue is sometimes caused by adding code for a control on your form, then deleting the control and leaving the code. Try commneting code for once so that you will get idea what exactly is causing this error.

Check this link which discussed the same:

http://social.msdn.microsoft.com/forums/en-US/vsx/thread/dbe2e211-2263-4dee-8e0d-428cabe8119b/

Another possible reason is that you can receive this error when you are creating your component or control on the design surface from the Toolbox. The most likely cause is that you are trying to use a component or control that was built to a 64-bit assembly. The Visual Studio design environment does not support 64-bit components.

Upvotes: 1

Related Questions