469,631 Members | 1,253 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,631 developers. It's quick & easy.

error BC30311: Value of type 'x' cannot be converted to 'x'

I am getting the following error during run-time
compilation or a rebuild all of my application:

error BC30311: Value of type 'mynamespace.x' cannot be
converted to 'mynamespace.x'

This occurs in only one component/project that accesses
the 'x' object whereas several other components/projects
also use the 'x' object in several other locations in
exactly the same way without any problems. If I Rebuild
ONLY this component it compiles without error, but on the
next Run compile the error returns. It shows up briefly in
the Build Error tasks and then disappears. Odd (I think).

Any suggestions?

Thanks,

David

Nov 20 '05 #1
9 40762
Either use an alias for the namespace or using fully qualified identifiers
in your code.

Regards - OHM

David wrote:
I am getting the following error during run-time
compilation or a rebuild all of my application:

error BC30311: Value of type 'mynamespace.x' cannot be
converted to 'mynamespace.x'

This occurs in only one component/project that accesses
the 'x' object whereas several other components/projects
also use the 'x' object in several other locations in
exactly the same way without any problems. If I Rebuild
ONLY this component it compiles without error, but on the
next Run compile the error returns. It shows up briefly in
the Build Error tasks and then disappears. Odd (I think).

Any suggestions?

Thanks,

David


--
Best Regards - OHM

O_H_M{at}BTInternet{dot}com
Nov 20 '05 #2
thank you. unfortunately I had already tried this approach
and it failed to make a difference:

I have tried:
Imports mynamespace.x
and then a direct reference to 'x'

as well as a fully qualified reference to 'x'

both failed.

Any other thoughts?

Thanks,

David
-----Original Message-----
Either use an alias for the namespace or using fully qualified identifiersin your code.

Regards - OHM

David wrote:
I am getting the following error during run-time
compilation or a rebuild all of my application:

error BC30311: Value of type 'mynamespace.x' cannot be
converted to 'mynamespace.x'

This occurs in only one component/project that accesses
the 'x' object whereas several other components/projects
also use the 'x' object in several other locations in
exactly the same way without any problems. If I Rebuild
ONLY this component it compiles without error, but on the next Run compile the error returns. It shows up briefly in the Build Error tasks and then disappears. Odd (I think).
Any suggestions?

Thanks,

David


--
Best Regards - OHM

O_H_M{at}BTInternet{dot}com
.

Nov 20 '05 #3
If this is a clash, then dont use the imports statement. In each case use
the fully qualified id

If you are fully qualifying the identifier in each instance which it is
referred, then it cannot be a clash between namespaces, something else must
be going on. The fact that you were able to compile it once suggest that
there may be some declarative dependency ( a bug ).

One suggestion may be to create a new project and re-add all the resources
and see if this clears the problem. Most odd !

Regards - OHM

David wrote:
thank you. unfortunately I had already tried this approach
and it failed to make a difference:

I have tried:
Imports mynamespace.x
and then a direct reference to 'x'

as well as a fully qualified reference to 'x'

both failed.

Any other thoughts?

Thanks,

David
-----Original Message-----
Either use an alias for the namespace or using fully qualified
identifiers in your code.

Regards - OHM

David wrote:
I am getting the following error during run-time
compilation or a rebuild all of my application:

error BC30311: Value of type 'mynamespace.x' cannot be
converted to 'mynamespace.x'

This occurs in only one component/project that accesses
the 'x' object whereas several other components/projects
also use the 'x' object in several other locations in
exactly the same way without any problems. If I Rebuild
ONLY this component it compiles without error, but on the
next Run compile the error returns. It shows up briefly in
the Build Error tasks and then disappears. Odd (I think).

Any suggestions?

Thanks,

David


--
Best Regards - OHM

O_H_M{at}BTInternet{dot}com
.


--
Best Regards - OHM

O_H_M{at}BTInternet{dot}com
Nov 20 '05 #4
Thanks for taking the time to respond. I'll give it a try.

David
-----Original Message-----
If this is a clash, then dont use the imports statement. In each case usethe fully qualified id

If you are fully qualifying the identifier in each instance which it isreferred, then it cannot be a clash between namespaces, something else mustbe going on. The fact that you were able to compile it once suggest thatthere may be some declarative dependency ( a bug ).

One suggestion may be to create a new project and re-add all the resourcesand see if this clears the problem. Most odd !

Regards - OHM

David wrote:
thank you. unfortunately I had already tried this approach and it failed to make a difference:

I have tried:
Imports mynamespace.x
and then a direct reference to 'x'

as well as a fully qualified reference to 'x'

both failed.

Any other thoughts?

Thanks,

David
-----Original Message-----
Either use an alias for the namespace or using fully qualified identifiers in your code.

Regards - OHM

David wrote:
I am getting the following error during run-time
compilation or a rebuild all of my application:

error BC30311: Value of type 'mynamespace.x' cannot be
converted to 'mynamespace.x'

This occurs in only one component/project that accesses the 'x' object whereas several other components/projects also use the 'x' object in several other locations in
exactly the same way without any problems. If I Rebuild ONLY this component it compiles without error, but on the next Run compile the error returns. It shows up briefly in the Build Error tasks and then disappears. Odd (I think).
Any suggestions?

Thanks,

David

--
Best Regards - OHM

O_H_M{at}BTInternet{dot}com
.


--
Best Regards - OHM

O_H_M{at}BTInternet{dot}com
.

Nov 20 '05 #5
* "David" <dr*****@no-spam.hotmail.com> scripsit:
I am getting the following error during run-time
compilation or a rebuild all of my application:

error BC30311: Value of type 'mynamespace.x' cannot be
converted to 'mynamespace.x'

This occurs in only one component/project that accesses
the 'x' object whereas several other components/projects
also use the 'x' object in several other locations in
exactly the same way without any problems. If I Rebuild
ONLY this component it compiles without error, but on the
next Run compile the error returns. It shows up briefly in
the Build Error tasks and then disappears. Odd (I think).


Are you using more than one project in the same solution? Maybe
changing the build order helps (right-click the solution and choose the
appropriate menu item). Are you sure there is no name conflict?

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>
Nov 20 '05 #6
Hi David,

I agree with Herfried's suggestion.
Have you tried that?Did that work for you?
If no, you may try to create a new project and declare a new namespace to
see if the problem persists, and then add the code line from your original
namespace project step by step to see what cause the error.

If you have any concern on this issue, please post here.

Regards,
Peter Huang
Microsoft Online Partner Support
Get Secure! www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Nov 20 '05 #7
Thank you gentlemen for taking the time to respond.

I went back and changed all of my references from these
components from the Actual DLL (rerferenced from the Bin
of that specific project) to the DLL under the projects
tab instead and it all seems to be running okay now.

Thanks for your suggestions.

David
-----Original Message-----
Hi David,

I agree with Herfried's suggestion.
Have you tried that?Did that work for you?
If no, you may try to create a new project and declare a new namespace tosee if the problem persists, and then add the code line from your originalnamespace project step by step to see what cause the error.
If you have any concern on this issue, please post here.

Regards,
Peter Huang
Microsoft Online Partner Support
Get Secure! www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
.

Nov 20 '05 #8
* "David" <dr*****@no-spam.hotmail.com> scripsit:
I went back and changed all of my references from these
components from the Actual DLL (rerferenced from the Bin
of that specific project) to the DLL under the projects
tab instead and it all seems to be running okay now.


Thank you for sharing this experience with us.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>
Nov 20 '05 #9

Hi,
I run into same problem. I even tried this approach to use PROJEC
REFERENCE instead of file reference. But it failed. I checked o
Microsoft sute http://tinyurl.com/5hwpp I used this hint, used fil
refernce and it worked. However in some other scenario (i have about 2
projects:some C# and some VB.Net) it failed and i had to go back t
project references.
So i think best solution is - try first project reference, if it doe
not work, try file reference. Either of them is guanranteed to work
as per my experience.

Thanks
Ravi

David wrote:
*Thank you gentlemen for taking the time to respond.

I went back and changed all of my references from these
components from the Actual DLL (rerferenced from the Bin
of that specific project) to the DLL under the projects
tab instead and it all seems to be running okay now.

Thanks for your suggestions.

David
-----Original Message-----
Hi David,

I agree with Herfried's suggestion.
Have you tried that?Did that work for you?
If no, you may try to create a new project and declare a

new namespace to
see if the problem persists, and then add the code line

from your original
namespace project step by step to see what cause the

error.

If you have any concern on this issue, please post here.

Regards,
Peter Huang
Microsoft Online Partner Support
Get Secure! www.microsoft.com/security
This posting is provided "as is" with no warranties and

confers no rights.

.

-
raviraj_b
-----------------------------------------------------------------------
Posted via http://www.mcse.m
-----------------------------------------------------------------------
View this thread: http://www.mcse.ms/message245902.htm

Nov 21 '05 #10

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by eelis.net | last post: by
3 posts views Thread by news.microsoft.com | last post: by
2 posts views Thread by andy6 via DotNetMonster.com | last post: by
reply views Thread by =?Utf-8?B?RGFuZGFuIFpoYW5n?= | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.